LiveActive security incident?Get immediate response
CVE Record

CVE-2025-31474: WordPress WP Database Optimizer plugin <= 1.2.1.3 - Cross Site Request Forgery (CSRF) Vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in matthewprice1178 WP Database Optimizer wp-database-optimizer allows Cross Site Request Forgery.This issue affects WP Database Optimizer: from n/a through <= 1.2.1.3.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a CSRF issue in the WordPress WP Database Optimizer plugin through version 1.2.1.3. An attacker would need to trick a logged-in user into taking an action, so risk depends on administrator exposure and plugin use.

Executive priority

Treat as a targeted WordPress hygiene issue, not an emergency based on current evidence. Prioritize sites using the plugin, especially business-critical WordPress properties with multiple administrators.

Technical view

CVE-2025-31474 is CWE-352 affecting wp-database-optimizer through <=1.2.1.3. CVSS 3.1 is 4.3 with network attack vector, low complexity, no privileges, required user interaction, unchanged scope, low integrity impact, and no confidentiality or availability impact.

Likely exposure

Exposure is limited to WordPress sites running WP Database Optimizer version 1.2.1.3 or earlier. The provided sources do not identify CPEs, a fixed version, or detailed vulnerable endpoints.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Exploitation requires user interaction, consistent with CSRF, and impact is described as limited integrity impact.

Researcher notes

Evidence is sparse. The record names CSRF and affected versions through <=1.2.1.3, but does not include endpoint details, proof of exploitation, patch version, or vendor advisory content in the provided bundle.

Mitigation direction

  • Inventory WordPress sites for WP Database Optimizer installations.
  • Check whether installed versions are 1.2.1.3 or earlier.
  • Check vendor, WordPress, and Patchstack guidance for a fixed release.
  • Disable or remove the plugin if it is unnecessary.
  • Prioritize admin-session hygiene and avoid untrusted links while logged in.

Validation and detection

  • Confirm plugin presence and version across production WordPress sites.
  • Review whether the plugin is required for current operations.
  • Check CVE and Patchstack records for updated remediation guidance.
  • Review admin activity logs for unexpected database-optimization changes.
  • Track this CVE until a fixed-version statement is available.
Prepared
Confidence
medium
Sources
3

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-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 lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-31474 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (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:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2025-31474Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
matthewprice1178WP Database Optimizerwp-database-optimizer, 0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-352 · source CWE mapping

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.