CVE-2025-31763: WordPress Cache control by Cacholong Plugin <= 5.4.1 - Cross Site Request Forgery (CSRF) vulnerability
Cross-Site Request Forgery (CSRF) vulnerability in Preliot Cache control by Cacholong cache-control-by-cacholong allows Cross Site Request Forgery.This issue affects Cache control by Cacholong: from n/a through <= 5.4.1.
Security readout for executives and security teams
Plain-English summary
This is a medium-severity CSRF issue in the WordPress Cache control by Cacholong plugin through version 5.4.1. A successful attack could cause an unintended state-changing action, but the cited CVSS data indicates low integrity impact and no confidentiality or availability impact.
Executive priority
Treat this as a moderate WordPress plugin risk. It is not confirmed as exploited in the supplied sources, but affected sites should be inventoried and remediated or have the plugin disabled where practical.
Technical view
CVE-2025-31763 is CWE-352 affecting Preliot cache-control-by-cacholong through <=5.4.1. CVSS 3.1 is 4.3: network reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, no confidentiality or availability impact, and low integrity impact.
Likely exposure
Exposure is limited to WordPress sites with Cache control by Cacholong installed at version 5.4.1 or earlier. The source bundle does not identify specific vulnerable actions, required victim role, or deployment prevalence.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. CSRF generally requires a victim interaction, and this CVE’s vector confirms user interaction is required. No exploit details are included in the source bundle.
Researcher notes
Evidence is sparse. The bundle confirms product, affected range, CWE, CVSS, and Patchstack reference, but not the vulnerable endpoint, nonce failure details, exploit maturity, or fixed version. Avoid claims beyond that evidence.
Mitigation direction
Inventory WordPress sites for cache-control-by-cacholong and affected versions.
Check Patchstack, CVE, and vendor guidance for a confirmed patched version.
Disable the plugin where operationally acceptable until remediation guidance is confirmed.
Prioritize sites with active administrative WordPress users.
Do not assume a fixed release without vendor confirmation.
Validation and detection
Confirm whether Cache control by Cacholong is installed on each WordPress site.
Record installed plugin versions and flag versions <=5.4.1.
Review security tooling for CVE-2025-31763 or Patchstack detections.
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.
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.
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.
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.