HomeWordPress vulnerabilitiesMolongui Authorship
Molongui Authorship vulnerabilities
Molongui Authorship has 2 known vulnerabilities in this database. The most recent published record is dated 10 Oct 2026.
- Known vulnerabilities
- 2
- Active installs
- 10,000+
- Latest version
- 5.2.12
- Last updated
- 11 Sep 2026
- Most recent
- 10 Oct 2026
No fixed version has been published yet, so consider disabling, removing or replacing the plugin until a safe release is available.
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-101920 | High 7.2 | Up to 5.2.12 | No fixed version yet | 2 d ago |
| Sensitive data exposure CVE-2023-7014 | Medium 5.3 | Before 4.7.5 | Fixed in 4.7.5 | 5 Feb 2024 |
Read the published descriptions
- CVE-2026-101920, 10 Oct 2026
- The Molongui Authorship - Author Boxes, Guest Authors & Co-Authors for WordPress plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'comment (href attribute inside comment content)' parameter in all versions up to, and including, 5.2.12 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is exploitable in the free build because the plugin's author-filter rewriter never appends the ?m_bm=true marker to its own anchors (Plugin::has_pro() returns false), meaning every href the byline script selects and rewrites is fully attacker-controlled. CVE record
- CVE-2023-7014, 5 Feb 2024
- The Author Box, Guest Author and Co-Authors for Your Posts - Molongui plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 4.7.4 via the 'ma_debu' parameter. This makes it possible for unauthenticated attackers to extract sensitive data including post author emails and names if applicable. CVE record
What to do if you run Molongui Authorship
If you run Molongui Authorship, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Molongui Authorship vulnerabilities
Free. We email you when a new vulnerability is published for Molongui Authorship, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.