LiveActive security incident?Get immediate response
CVE Record

CVE-2025-31079: WordPress Usermaven plugin <= 1.2.1 - Cross Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in usermaven Usermaven usermaven allows Cross Site Request Forgery.This issue affects Usermaven: from n/a through <= 1.2.1.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-31079 is a CSRF issue in the WordPress Usermaven plugin through version 1.2.1. A successful attack could cause a logged-in user to perform an unintended action, but the published scoring indicates limited integrity impact and no stated confidentiality or availability impact.

Executive priority

Treat this as a moderate-priority WordPress plugin exposure. It is not presented as actively exploited in the supplied sources, but vulnerable internet-facing WordPress sites should still be inventoried and remediated during normal patch cycles.

Technical view

The CVE describes CWE-352 Cross-Site Request Forgery in Usermaven for WordPress, affecting versions up to and including 1.2.1. CVSS 3.1 is 4.3 with network attack vector, low complexity, no attacker privileges, required user interaction, unchanged scope, and low integrity impact.

Likely exposure

Exposure is likely limited to WordPress sites where the Usermaven plugin is installed and running at version 1.2.1 or earlier. The bundle does not identify other products or platforms as affected.

Exploitation context

The source bundle does not show active exploitation, and the CVE is not marked as CISA KEV. Exploitation requires user interaction, consistent with CSRF, but the provided sources do not describe exploit maturity or real-world abuse.

Researcher notes

Evidence is limited to the CVE metadata and Patchstack vulnerability entry. The bundle provides affected range, CWE, CVSS, and impact class, but does not provide endpoint details, proof-of-concept status, exploit telemetry, or a named fixed version.

Mitigation direction

  • Inventory WordPress sites for the Usermaven plugin and record installed versions.
  • Check Usermaven or Patchstack guidance for a fixed version or official mitigation.
  • Update if an official fixed release is available from the vendor.
  • Disable or remove the plugin if it is not business-critical.
  • Review administrator workflows for unexpected Usermaven-related changes.

Validation and detection

  • Confirm whether Usermaven is installed on each WordPress property.
  • Verify plugin versions and flag any instance at 1.2.1 or earlier.
  • Check vendor and Patchstack pages for current remediation details.
  • Review WordPress admin activity for unexpected plugin configuration changes.
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
cve · low confidence lookup

CVE-2025-31079 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-31079Attack 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
usermavenUsermavenusermaven, 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.