CVE-2025-31742: WordPress Dima Take Action Plugin <= 1.0.5 - Cross Site Scripting (XSS) vulnerability
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in PixelDima Dima Take Action dima-take-action allows Stored XSS.This issue affects Dima Take Action: from n/a through <= 1.0.5.
Security readout for executives and security teams
Plain-English summary
CVE-2025-31742 is a stored cross-site scripting issue in the WordPress Dima Take Action plugin through version 1.0.5. A highly privileged user could store unsafe content that runs in another user’s browser after interaction. This is not listed as known exploited in CISA KEV.
Executive priority
Prioritize within normal vulnerability remediation cycles, faster for public-facing WordPress sites or sites with many privileged users. Business risk is mainly account trust, content integrity, and visitor/session exposure from stored browser-side script execution.
Technical view
The issue is CWE-79 improper input neutralization during web page generation in PixelDima Dima Take Action, package dima-take-action, affecting versions through 1.0.5. CVSS 3.1 is 5.9: network reachable, low complexity, high privileges required, user interaction required, changed scope, and low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to WordPress sites with the Dima Take Action plugin installed at version 1.0.5 or earlier. The provided sources do not identify affected hosting providers, themes, or bundled distributions.
Exploitation context
The CVSS vector indicates exploitation requires high privileges and user interaction. The source bundle does not show public exploitation, KEV listing, exploit code, or confirmed attacks. Treat this as a credible stored XSS risk, not proven active exploitation.
Researcher notes
Evidence is concise: CVE metadata and Patchstack identify stored XSS, affected plugin, and CVSS details. The bundle does not provide vulnerable parameter names, proof-of-concept details, fixed version, or vendor changelog. Avoid assuming exploitability beyond the CVSS requirements.
Mitigation direction
Inventory WordPress sites for dima-take-action and version 1.0.5 or earlier.
Check PixelDima and Patchstack guidance for a fixed release or mitigation.
Update the plugin if a vendor-supported fixed version is available.
Disable or remove the plugin where it is not business-critical.
Restrict plugin administration to trusted, necessary WordPress users only.
Validation and detection
Confirm whether the Dima Take Action plugin is installed on each WordPress site.
Record installed plugin versions and flag version 1.0.5 or earlier.
Review privileged WordPress accounts that can configure or edit plugin content.
Inspect affected pages for unexpected scripts or injected markup.
Monitor vendor and Patchstack advisories for updated remediation details.
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-79: 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-79 · source CWE mapping
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.