CVE-2026-101920 molongui CVE debrief

Who should care

WordPress administrators and users of the Molongui Authorship plugin should assess exposure and prioritize updating to a fixed version. Additionally, defenders should verify and update Molongui Authorship plugin versions to prevent exploitation and implement additional security measures such as input sanitization and output escaping.

Why it matters

The Molongui Authorship plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting, allowing unauthenticated attackers to inject arbitrary web scripts.

• Unauthenticated attackers can inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
• Successful exploitation could lead to user session hijacking or unauthorized actions.
• Defenders should verify and update Molongui Authorship plugin versions to prevent exploitation.
• Additional security measures, such as input sanitization and output escaping, should be implemented.

Technical summary

The Molongui Authorship 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. The vulnerability is caused by the plugin's failure to properly sanitize and escape user input.

Defensive priority

Defenders should prioritize verifying and updating Molongui Authorship plugin versions to prevent exploitation.

Recommended defensive actions

• Verify Molongui Authorship plugin version and update to a fixed version if necessary
• Implement input sanitization and output escaping for comment content
• Monitor for suspicious activity and implement additional security measures
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, including the affected versions and parameters. The vulnerability 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. Defenders should verify and update Molongui Authorship plugin versions to prevent exploitation and implement additional security measures such as Web

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.