Security readout for executives and security teams
Plain-English summary
This CVE is a reflected XSS issue in the WordPress Eli's WordCents adSense Widget with Analytics plugin through 1.3.03.27. An attacker would need a user to interact with a malicious link or request. Successful exploitation could expose limited data, alter page behavior, or disrupt user sessions.
Executive priority
Prioritize this for internet-facing WordPress sites using the plugin, especially administrator-facing sites. It is not described as actively exploited, but the issue is high severity and unauthenticated, with user interaction as the main limiting factor.
Technical view
The source bundle describes unauthenticated reflected Cross-Site Scripting, CWE-79, affecting the WordPress plugin wordcents through 1.3.03.27. CVSS 3.1 is 7.1 with network access, low complexity, no privileges, required user interaction, changed scope, and low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is likely limited to WordPress sites that have Eli's WordCents adSense Widget with Analytics, package wordcents, installed at version 1.3.03.27 or earlier and reachable by users or attackers.
Exploitation context
The bundle does not show CISA KEV listing or any cited evidence of active exploitation. The CVSS vector indicates exploitation requires user interaction, consistent with reflected XSS. No exploit details or weaponized guidance are provided in the sources.
Researcher notes
Evidence is narrow: CVE metadata and Patchstack entry identify reflected XSS in wordcents through 1.3.03.27. The bundle does not include payloads, affected endpoints, patch version, or exploitation telemetry. Do not infer stored XSS, RCE, or broad WordPress impact.
Mitigation direction
Inventory WordPress sites for the wordcents plugin and affected versions.
Check Patchstack or vendor guidance for a fixed version or workaround.
Disable or remove the plugin where it is not business-critical.
Use WAF and URL filtering as temporary compensating controls.
Warn administrators against following unsolicited links to affected WordPress sites.
Validation and detection
Confirm plugin presence and version in WordPress admin or asset inventory.
Verify affected versions are upgraded, disabled, or removed.
Review web logs for unusual requests targeting plugin-related paths.
Do not claim active exploitation without KEV or cited evidence.
Recheck vendor guidance because the source bundle lacks fix details.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.