Security readout for executives and security teams
Plain-English summary
CVE-2025-23801 affects the WordPress Style Admin plugin by FuzzGuard through version 1.4.3. A tricked user could unintentionally trigger a change that stores malicious script in the site. Impact is limited but meaningful: visitor or administrator browsers may run attacker-controlled code within the WordPress site context.
Executive priority
Treat this as a high-priority WordPress plugin exposure if Style Admin is installed. The business risk is site trust and administrator-session compromise through stored browser-side code, but urgency depends on confirmed deployment and vendor fix availability.
Technical view
The source describes a CSRF weakness in style-admin that can lead to stored XSS. CVSS 3.1 is 7.1, network exploitable, low complexity, no privileges required, and user interaction required. The bundle names CWE-352 and does not provide exploit details, affected endpoints, nonce behavior, or a confirmed fixed version.
Likely exposure
Exposure is limited to WordPress sites with the FuzzGuard Style Admin plugin installed at version 1.4.3 or earlier. The bundle does not identify other affected products or platforms.
Exploitation context
The CVE is not listed as KEV in the bundle, and no cited source here supports active exploitation. Exploitation requires user interaction and appears to rely on CSRF leading to persistent script execution.
Researcher notes
Evidence is sparse. The bundle establishes CSRF to stored XSS in Style Admin through 1.4.3, CVSS 7.1, CWE-352, and no KEV flag. It does not include PoC status, fixed version, vulnerable parameter, authentication context, or remediation detail.
Mitigation direction
- Inventory WordPress sites for the style-admin plugin.
- Confirm whether installed versions are 1.4.3 or earlier.
- Check FuzzGuard and Patchstack guidance for a fixed release or mitigation.
- Prioritize removal or disablement where no business need exists.
- Avoid relying on exploit testing as proof of safety.
Validation and detection
- Review plugin inventory across production, staging, and managed WordPress hosting.
- Record Style Admin version and deployment location for each site.
- Check vendor or Patchstack records for fixed-version guidance.
- Review recent WordPress admin changes for unexpected Style Admin modifications.
- Confirm compensating controls do not replace patch status.
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-2025-23801 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
- 7.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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.
SSVC decision data
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:C/C:L/I:L/A:L2.83.7PatchstackVulnerability scoring details
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://patchstack.com/database/Wordpress/Plugin/style-admin/vulnerability/wordpress-style-admin-plugin-1-4-3-csrf-to-stored-xss-vulnerability?_s_id=cveCVE reference, Patchstack · vdb-entry
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.