Security readout for executives and security teams
Plain-English summary
CVE-2025-23797 is reported as a critical CSRF flaw in the WordPress WP Options Editor plugin through version 1.1. The CVE says it can lead to privilege escalation, meaning a compromised workflow could result in unauthorized elevated access to a WordPress site.
Executive priority
Prioritize this as urgent only where the plugin is present. The business concern is unauthorized privilege escalation in WordPress, which can lead to site takeover, content tampering, or operational disruption.
Technical view
The issue is categorized as CWE-352 Cross-Site Request Forgery in Mike Selander WP Options Editor, package wp-options-editor, affecting versions through 1.1. The record assigns CVSS 3.1 score 9.8 with high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to WordPress sites with WP Options Editor installed at version 1.1 or earlier. The source bundle does not identify affected hosting platforms, themes, or other plugins.
Exploitation context
The source bundle does not state active exploitation, and KEV is false. Details are sparse: the CVE labels this as CSRF, but the provided CVSS vector lists UI:N, so validation should rely on vendor or Patchstack details.
Researcher notes
Evidence is limited to the CVE record and Patchstack reference. No exploit details, patch version, or active exploitation evidence is provided. The affected metadata is less clear than the description, which names versions through 1.1.
Mitigation direction
- Inventory WordPress sites for the wp-options-editor plugin.
- Check Patchstack and vendor guidance for a fixed release or advisory update.
- If no supported fixed version exists, disable or remove the plugin.
- Prioritize externally reachable and business-critical WordPress sites first.
- Review WordPress administrative access controls and least-privilege assignments.
Validation and detection
- Confirm whether WP Options Editor is installed and active.
- Record the installed plugin version on each WordPress site.
- Check whether any site runs version 1.1 or earlier.
- Review WordPress user roles for unexpected privilege changes.
- Monitor vendor and Patchstack references for updated remediation details.
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 lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-23797 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
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
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:N/S:U/C:H/I:H/A:H3.95.9PatchstackVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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/wp-options-editor/vulnerability/wordpress-wp-options-editor-plugin-1-1-csrf-to-privilege-escalation-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.