Security readout for executives and security teams
Plain-English summary
This is a CSRF flaw in the WordPress DN Footer Contacts plugin. A logged-in site administrator could be tricked into causing an unintended low-impact change if they visit attacker-controlled content. The sources do not describe data theft, service outage, or active exploitation.
Executive priority
Handle during the next routine WordPress maintenance cycle unless the plugin manages sensitive business content or high-trust public contact workflows. Prioritize inventory first because impact appears limited but depends on plugin deployment.
Technical view
CVE-2025-31839 is CWE-352 in digireturn DN Footer Contacts, package dn-footer-contacts, affecting versions through 1.8.1 per the CVE description. CVSS 3.1 is 4.3: network reachable, low complexity, no privileges required, user interaction required, low integrity impact only.
Likely exposure
Exposure is limited to WordPress sites that have the DN Footer Contacts plugin installed at an affected version. Sites without this plugin are not indicated as affected by the provided sources.
Exploitation context
The bundle does not report known exploitation, and KEV status is false. Exploitation requires user interaction, likely involving a privileged WordPress user being induced to perform an unintended request.
Researcher notes
Source detail is sparse: the public bundle names CSRF, affected plugin, CVSS vector, and Patchstack reference, but does not describe the exact vulnerable action or a named fixed version. Avoid assuming exploitability beyond low integrity impact and required user interaction.
Mitigation direction
Inventory WordPress sites for the DN Footer Contacts plugin.
Check vendor or Patchstack guidance for a fixed version or official workaround.
Update the plugin if a maintained fixed release is available.
Disable or remove the plugin where it is not business-critical.
Restrict administrative access and reinforce anti-phishing controls for WordPress administrators.
Validation and detection
Confirm whether dn-footer-contacts is installed on each WordPress site.
Record installed plugin versions and flag versions through 1.8.1.
Review available WordPress logs for unexpected plugin-related changes.
Verify vendor guidance before marking remediation complete.
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.