Molongui Authorship at a glance
- 7 publicly disclosed vulnerabilities, 1 of them rated High or Critical. The most recent was disclosed on Oct 9, 2026.
- Ranked #1711 by popularity on WordPress.org (10,000+ active installs).
- The latest version is 5.3.2 (released Oct 8, 2026). The most recent security fix shipped in 5.3.0.
- Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
- The first thing to do: update to the latest version and turn on automatic updates.
Check your Molongui Authorship version
Enter the Molongui Authorship version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.
Your version number is compared on this page only. It is not sent anywhere.
Get an email when a new vulnerability is disclosed
We'll tell you when a new vulnerability is disclosed in “Molongui Authorship”, with the version that fixes it. Free, email address only, stop any time.
We use your email address only for these alerts. Privacy policy
Want every plugin and theme on your site checked daily?
With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.
How to check whether your site is affected
- 1
Find your version
In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Molongui Authorship”.
- 2
Compare it with the list below
If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.
- 3
Update
Click “Update now” to move to the latest version (5.3.2). Taking a backup first is a good idea.
- 4
Turn on automatic updates
On the same screen, click “Enable auto-updates” so future fixes are installed automatically.
Known Molongui Authorship vulnerabilities
Molongui Authorship <= 5.2.12 - Unauthenticated Stored DOM-Based Cross-Site Scripting via Comment href Attribute
Cross-site scripting (XSS) · CVE-2026-101920
Affected versions: ≤ 5.2.12
Fixed in: 5.3.0
Severity: High 7.2 · Disclosed Oct 9, 2026
Molongui <= 4.7.7 - Authenticated (Author+) Insecure Direct Object Reference
Missing authorization · CVE-2024-30507
Affected versions: ≤ 4.7.7
Fixed in: 4.7.8
Severity: Medium 4.3 · Disclosed Mar 28, 2024
Molongui <= 4.7.7 - Authenticated (Author+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2024-29764
Affected versions: ≤ 4.7.7
Fixed in: 4.7.8
Severity: Medium 5.5 · Disclosed Mar 25, 2024
Author Box, Guest Author and Co-Authors for Your Posts – Molongui <= 4.7.4 - Information Exposure via ma_debug
Information disclosure · CVE-2023-7014
Affected versions: ≤ 4.7.4
Fixed in: 4.7.5
Severity: Medium 5.3 · Disclosed Jan 16, 2024
Molongui <= 4.7.3 - Missing Authorization
Missing authorization · CVE-2023-50876
Affected versions: ≤ 4.7.3
Fixed in: 4.7.4
Severity: Medium 5.4 · Disclosed Dec 26, 2023
Molongui <= 4.6.19 - Authenticated (Administrator+) Stored Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2023-39921
Affected versions: ≤ 4.6.19
Fixed in: 4.6.20
Severity: Medium 4.4 · Disclosed Nov 28, 2023
Molongui <= 4.6.19 - Reflected Cross-Site Scripting
Cross-site scripting (XSS) · CVE-2023-39164
Affected versions: ≤ 4.6.19
Fixed in: 4.6.20
Severity: Medium 6.1 · Disclosed Jul 26, 2023
| Vulnerability | Affected versions | Fixed in | Severity | Disclosed |
|---|---|---|---|---|
| Molongui Authorship <= 5.2.12 - Unauthenticated Stored DOM-Based Cross-Site Scripting via Comment href AttributeCross-site scripting (XSS) · CVE-2026-101920 | ≤ 5.2.12 | 5.3.0 | High 7.2 | Oct 9, 2026 |
| Molongui <= 4.7.7 - Authenticated (Author+) Insecure Direct Object ReferenceMissing authorization · CVE-2024-30507 | ≤ 4.7.7 | 4.7.8 | Medium 4.3 | Mar 28, 2024 |
| Molongui <= 4.7.7 - Authenticated (Author+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2024-29764 | ≤ 4.7.7 | 4.7.8 | Medium 5.5 | Mar 25, 2024 |
| Author Box, Guest Author and Co-Authors for Your Posts – Molongui <= 4.7.4 - Information Exposure via ma_debugInformation disclosure · CVE-2023-7014 | ≤ 4.7.4 | 4.7.5 | Medium 5.3 | Jan 16, 2024 |
| Molongui <= 4.7.3 - Missing AuthorizationMissing authorization · CVE-2023-50876 | ≤ 4.7.3 | 4.7.4 | Medium 5.4 | Dec 26, 2023 |
| Molongui <= 4.6.19 - Authenticated (Administrator+) Stored Cross-Site ScriptingCross-site scripting (XSS) · CVE-2023-39921 | ≤ 4.6.19 | 4.6.20 | Medium 4.4 | Nov 28, 2023 |
| Molongui <= 4.6.19 - Reflected Cross-Site ScriptingCross-site scripting (XSS) · CVE-2023-39164 | ≤ 4.6.19 | 4.6.20 | Medium 6.1 | Jul 26, 2023 |
Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Oct 9, 2026.
Most common weaknesses in Molongui Authorship
Cross-site scripting (XSS)
4 issues
An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.
Missing authorization
2 issues
Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.
Information disclosure
1 issue
Data that should stay private, such as user details or configuration values, can be read from outside.
Frequently asked questions
Is Molongui Authorship safe to use?
Molongui Authorship is a well-known plugin with 10,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (5.3.2) and turn on automatic updates.
How do I find which version of Molongui Authorship my site is running?
In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.
Could updating break my site?
Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.
Can I check all my other plugins too?
Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.
Check every plugin and theme automatically, every day
Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.
Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.
← All plugin vulnerabilitiesMolongui Authorship on WordPress.org