Security readout for executives and security teams
Plain-English summary
Stetic for WordPress up to version 1.0.6 allowed a forged request to change plugin-controlled content and store malicious script. A successful attack would require user interaction, but could affect website visitors or administrators once stored.
Executive priority
Treat this as a high-priority WordPress plugin exposure if Stetic is deployed. The main business risk is persistent script injection on a public website, potentially affecting trust, sessions, and site integrity.
Technical view
The vulnerability is a CSRF flaw in Stetic's stats_page function caused by missing nonce validation. The reported impact is stored cross-site scripting, allowing arbitrary web scripts in affected versions up to and including 1.0.6.
Likely exposure
Exposure is limited to WordPress sites running the Stetic plugin version 1.0.6 or earlier. Sites without this plugin are not affected based on the provided sources.
Exploitation context
The CVSS vector indicates network reachability, low complexity, no attacker privileges, and required user interaction. The bundle says CISA KEV is false, and no cited source confirms active exploitation.
Researcher notes
Evidence identifies CWE-352 and stored XSS via missing nonce validation in stats_page. The sources do not name a fixed version, exploit-in-the-wild evidence, or detailed remediation beyond the affected version statement.
Mitigation direction
- Inventory WordPress sites for the Stetic plugin and affected versions.
- Remove or disable Stetic if it is unnecessary or unmaintained.
- Check Wordfence, WordPress plugin, and vendor guidance for fixed release information.
- Review affected sites for unexpected stored scripts or plugin setting changes.
- Harden administrator sessions and avoid clicking untrusted links while remediation is pending.
Validation and detection
- Confirm whether Stetic is installed and enabled on each WordPress site.
- Record the installed Stetic version and compare it with 1.0.6.
- Review plugin-managed pages or settings for unexpected script content.
- Check security monitoring for suspicious WordPress admin activity.
- Do not claim active exploitation without KEV or source evidence.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-352: 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.
Open ATT&CK lookupCVE-2021-42364 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://plugins.trac.wordpress.org/browser/stetic/trunk/stetic.php#L129CVE reference · x_refsource_MISC
- https://wordfence.com/vulnerability-advisories/#CVE-2021-42364CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.