Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSubmit comment with crafted href (unauthenticated)
-
DeliveryPlugin byline rewriter selects and rewrites anchor without pro marker
-
ExploitVictim loads injected page
-
ExecutionDOM-based script executes in victim browser
-
ImpactSteal session/credentials or deface in victim context
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the FREE build of the Molongui Authorship plugin (versions up to and including 5.2.12), where Plugin::has_pro() returns false so the author-filter rewriter never appends the ?m_bm=true marker to its own anchors - making every href the byline script rewrites fully attacker-controlled; the pro build is not affected by this specific path. The site must accept comment content (the 'comment' href-inside-comment-content parameter is the injection point), and comment submission must be reachable by unauthenticated users for the PR:N scenario to hold. The principal limiting factor is that payload execution is deferred and conditional on a victim loading the specific injected page (stored/DOM-based trigger), and exploitation is confined to deployments running the vulnerable free build with the byline/author-filter feature active. |
| Impact | The input CVSS 3.1 base score of 7.2 (High) reflects a network-reachable (AV:N), low-complexity (AC:L), unauthenticated (PR:N) stored XSS with a changed scope (S:C) and low confidentiality/integrity impact (C:L/I:L/A:N). The combination of PR:N and AC:L is the main driver of risk: an unauthenticated attacker can plant the payload via a comment, and the plugin's own byline/author-filter rewriter then rewrites the attacker-controlled href on every page view. However, no EPSS probability was supplied, the CVE is not present in CISA KEV (no active exploitation signal), and no public proof-of-concept is indicated in the provided data - so this is a high-CVSS finding without any corroborating real-world exploitation evidence at this time. One signal tension worth flagging: the vector uses UI:N, yet the description states the script executes 'whenever a user accesses an injected page,' which is a form of victim browsing - some analysts would score this UI:R, which would lower the base score. Exploitation is further gated by a specific condition (the free, non-pro build where Plugin::has_pro() returns false). Net assessment: a credible, vendor-reported (Wordfence) stored XSS that merits patching on the normal cycle, but absent EPSS/KEV/POC it is a 'patch-soon' issue rather than an emergency, and its realistic footprint is bounded by the free-build requirement and the need for a victim to load the affected page. |
| Exploit ScenarioDerived | An unauthenticated attacker submits a blog comment on a site running the free build of Molongui Authorship, embedding a malicious href inside the comment content. Because the plugin's author-filter byline script rewrites that anchor without appending the pro-only ?m_bm=true marker, the attacker fully controls the rewritten link, and the DOM-based payload executes in the browser of any user who later views the injected page. No public exploit code is indicated in the supplied data, but exploitation is low-complexity and requires no authentication. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 10, 2026
Stored DOM-based cross-site scripting in the Molongui Authorship - Author Boxes, Guest Authors & Co-Authors for WordPress plugin (free build, versions up to and including 5.2.12) lets unauthenticated attackers inject arbitrary web scripts via the href attribute inside comment content, which then execute in the browser of any visitor who loads the affected page. The flaw is confined to the free build: because Plugin::has_pro() returns false, the author-filter rewriter never appends its ?m_bm=true marker to plugin-generated anchors, so every href the byline script selects and rewrites is fully attacker-controlled. The assessed vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N (7.2 High) and no public exploit code identified at time of analysis.
RemediationAI
Vendor-released patch: upgrade the Molongui Authorship plugin to version 5.3.0, whose tag contains the updated byline script (assets/js/byline.849a.min.js) referenced from the advisory. Until the upgrade can be staged, restrict the affected surface: disable WordPress comment submission or require authentication for commenting (this removes the unauthenticated PR:N vector but suppresses legitimate engagement), and/or deactivate the plugin's byline/author-filter rendering on templates that display comment-derived links. A WAF or input filter that rejects href values containing javascript:, data:, vbscript: schemes or inline event-handler attributes can blunt known payloads, though it may produce false positives on benign links and does not remediate the underlying DOM sink. Re-check the plugin changelog and the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/1bf63dd3-9fd1-4b72-b7e0-48155312c48f?source=cve for any further fixed releases before relying solely on compensating controls.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The issue is a CWE-79 cross-site scripting defect with a DOM-based execution path grafted onto a stored injection point. Comment content is persisted by WordPress and later parsed in the browser by the plugin's front-end byline script (assets/js/byline.4cc4.min.js in the vulnerable 5.2.12 tag), which walks selected anchor elements and rewrites their href attributes. In the free build, has_pro() returns false, so the author-filter rewriter in includes/author-filters.php (see the referenced lines 29 and 464) never appends the ?m_bm=true marker that would otherwise distinguish plugin-generated links from user-supplied ones; consequently, the href value taken from the comment content is treated as trusted and written into the DOM without adequate sanitization or escaping, producing script execution in the victim's browser. The changed-scope (S:C) CVSS metric reflects that the injected script runs in the security context of the page rather than being contained to a single component. The 5.3.0 tag ships a revised byline script (assets/js/byline.849a.min.js), consistent with the fix being delivered there.
Know when Wordpress Plugin gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Unauthenticated comment injection (PR:N, AC:L) runs script in the victim's browser context yielding a scope change (S:C) with limited C/I and no availability impact, matching typical stored XSS.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
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.
Executive ViewAI
A high-severity stored cross-site scripting flaw in the free build of the Molongui Authorship WordPress plugin (versions up to and including 5.2.12) allows an unauthenticated party to plant malicious script in comment content that then runs in the browsers of ordinary site visitors. Because the plugin is widely embedded in public-facing WordPress sites and no vendor patch is available, every page view on an affected site is a potential delivery point for credential theft, session hijacking, or malicious redirects. Leadership should treat this as an external-facing brand and trust risk affecting customers, prospects, and any partner sites hosting the plugin, with remediation dependent on vendor release timing rather than an internal fix.
No vendor-released patch identified at time of analysis. Interim mitigations: deactivate or remove the free build of the plugin (affected through 5.2.12) on internet-facing sites; apply WAF or edge rules blocking script injection via the href attribute in comment content; enforce strict server-side comment HTML sanitization and moderation; deploy a restrictive Content-Security-Policy that blocks inline and untrusted script execution; and restrict or disable public commenting on high-value pages until a fixed version is confirmed.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
EUVD-2026-96277
GHSA-m398-mh86-wgcp
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB