LiveActive security incident?Get immediate response
CVE Record

CVE-2025-31439: WordPress Browser Caching with .htaccess 1.2.1 - Cross Site Request Forgery (CSRF) Vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in tobias_.MerZ Browser Caching with .htaccess allows Cross Site Request Forgery. This issue affects Browser Caching with .htaccess: from 1.2.1 through n/a.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-31439 is a medium-severity CSRF issue in the WordPress plugin Browser Caching with .htaccess version 1.2.1. It could let an attacker trick a user into making an unwanted plugin-related request, potentially causing limited integrity or availability impact. The supplied sources do not name a fixed version or active exploitation.

Executive priority

Treat this as a moderate WordPress hygiene issue, not an emergency from current evidence. Prioritize sites where the plugin is installed on externally reachable or business-critical WordPress properties, especially if there is no vendor-confirmed fixed release.

Technical view

The record describes CWE-352 in package browser-caching-with-htaccess, affecting version 1.2.1. CVSS 3.1 is 5.4 with network access, low complexity, no attacker privileges, required user interaction, and low integrity and availability impact. Source detail is limited, so affected functions and exact request behavior are not confirmed.

Likely exposure

Exposure is likely limited to WordPress sites running Browser Caching with .htaccess version 1.2.1. The source bundle lists default status as unaffected outside the affected entry and provides no CPEs, so asset discovery should rely on WordPress plugin inventory and package name matching.

Exploitation context

CISA KEV status is false in the supplied bundle, and no cited source states active exploitation. The CVSS vector requires user interaction, consistent with CSRF risk where a victim’s browser may be induced to send an unintended request. No exploit details are provided in the sources.

Researcher notes

The public bundle lacks endpoint, nonce, capability, and patch details. Avoid assuming administrator-only impact unless confirmed elsewhere. Validation should focus on version presence and vendor advisories rather than reproducing the CSRF behavior. Confidence is limited by sparse public technical detail.

Mitigation direction

  • Inventory WordPress sites for browser-caching-with-htaccess version 1.2.1.
  • Check vendor, WordPress plugin, and Patchstack guidance for a fixed or supported release.
  • If no supported fix exists, evaluate disabling or replacing the plugin.
  • Limit plugin administration to trusted users and hardened admin sessions.
  • Prioritize remediation on business-critical or internet-facing WordPress sites.

Validation and detection

  • Confirm installed plugin slug and version from WordPress asset inventory.
  • Review change logs or vendor guidance for a fixed version statement.
  • Check whether affected sites expose WordPress administration to untrusted networks.
  • Review logs for unexpected plugin configuration changes around privileged sessions.
  • Track CVE and Patchstack entries for updated technical detail.
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-31439 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
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

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
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2025-31439Attack 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:L

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
tobias_.MerZBrowser Caching with .htaccessbrowser-caching-with-htaccess, 1.2.1unaffected
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.