Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Rupok AwesomePress awesomepress allows Stored XSS.This issue affects AwesomePress: from n/a through <= 1.0.
Security readout for executives and security teams
Plain-English summary
AwesomePress for WordPress through version 1.0 has a stored XSS flaw. A logged-in attacker could save unsafe content that later runs in another user’s browser when viewed. Business risk is account abuse, content tampering, or limited data exposure inside affected WordPress administration or site workflows.
Executive priority
Treat as a medium-priority WordPress plugin issue. Prioritize internet-facing sites, sites with many contributor accounts, or sites where admin sessions could access sensitive business workflows.
Technical view
The CVE describes CWE-79 improper neutralization during page generation in Rupok AwesomePress. CVSS 3.1 is 6.5 with network access, low complexity, low privileges required, user interaction required, and changed scope. The provided sources identify affected AwesomePress versions through <=1.0 but do not identify a fixed version.
Likely exposure
Exposure is limited to WordPress installations that have the AwesomePress plugin installed at version 1.0 or earlier. The CVSS vector indicates exploitation requires an authenticated user or equivalent low privilege, plus a victim viewing the stored content.
Exploitation context
The source bundle does not show CISA KEV listing or cited active exploitation. The likely scenario is abuse by a low-privileged WordPress user who can store plugin-handled content later rendered to another user.
Researcher notes
Evidence is sparse. The bundle confirms stored XSS, CVSS 6.5, CWE-79, and affected versions through <=1.0. It does not provide vulnerable parameters, proof of concept details, exploitation in the wild, or a named fixed version.
Mitigation direction
Inventory WordPress sites for the AwesomePress plugin and installed version.
Check Patchstack and vendor guidance for an official fixed release or advisory.
Disable or remove AwesomePress where it is not business-critical.
Restrict plugin content-writing permissions to trusted users only.
Monitor WordPress content changes and admin activity for unexpected edits.
Validation and detection
Confirm whether any WordPress site runs AwesomePress version 1.0 or earlier.
Review plugin-managed fields and pages for unexpected script-like content.
Verify only trusted roles can create or edit affected plugin content.
Run safe staging XSS regression tests without production payloads.
Confirm no provided source identifies active exploitation or KEV status.
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.