Security readout for executives and security teams
Plain-English summary
This is a medium-severity CSRF issue in the Pagup WordPress Robots.Txt optimization plugin, reported for versions up to 1.4.5. It could let an attacker abuse a user’s browser to trigger unintended plugin actions. The public bundle does not describe the exact action, fixed version, or active exploitation.
Executive priority
Treat as a routine but time-bound WordPress hygiene issue. It is not presented as exploited, but affected SEO or robots.txt controls may influence site behavior. Prioritize inventory and remediation for externally managed or high-traffic WordPress properties.
Technical view
CVE-2023-25706 is CWE-352 in the WordPress Robots.Txt optimization plugin package better-robots-txt. CVSS 3.1 is 5.4 with network attack vector, low complexity, required user interaction, and low integrity and availability impact. Supplied affected-version metadata is sparse beyond the <=1.4.5 statement.
Likely exposure
Exposure is limited to WordPress sites that have the Pagup WordPress Robots.Txt optimization plugin installed, especially versions 1.4.5 or earlier. Sites without this plugin are not indicated as affected by the supplied sources.
Exploitation context
The source bundle does not report active exploitation, and KEV status is false. CSRF typically depends on tricking a user into making an unintended request, but the supplied sources do not describe exploit details or targeted plugin behavior.
Researcher notes
Do not assume a fixed version from the provided data. The CVSS vector supports user interaction and low integrity/availability impact, with no confidentiality impact. Further validation should focus on confirming plugin presence, version, and vendor remediation guidance.
Mitigation direction
- Inventory WordPress sites for the better-robots-txt plugin and installed version.
- Check Pagup, WordPress plugin, or Patchstack guidance for a fixed release or workaround.
- Disable or remove the plugin where business need is low or version safety cannot be verified.
- Restrict administrative access and reinforce anti-phishing controls for WordPress operators.
Validation and detection
- Confirm whether each WordPress site has the better-robots-txt plugin installed.
- Record plugin version and compare it with the <=1.4.5 affected statement.
- Review vendor or Patchstack advisories for remediation status before closing the finding.
- Check WordPress logs for unexpected plugin setting changes, if available.
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-2023-25706 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
- Medium
- CVSS
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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.
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:N/I:L/A:L2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
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.