Security readout for executives and security teams
Plain-English summary
The Visitor Counter WordPress plugin through version 1.4.3 has a CSRF issue that can lead to stored XSS. If an administrator is tricked into a harmful action, malicious script could be saved and later run in users' browsers.
Executive priority
Prioritize this for WordPress estates where the plugin is installed, especially public sites with multiple administrators. It is high severity, but the supplied evidence does not show known active exploitation.
Technical view
CVE-2025-31449 is CWE-352 in EricH The Visitor Counter. The reported impact is CSRF to stored XSS, with CVSS 3.1 score 7.1 and vector AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L.
Likely exposure
Exposure is limited to WordPress sites using The Visitor Counter plugin at version 1.4.3 or earlier. The bundle does not identify affected themes, WordPress core versions, or hosting platforms.
Exploitation context
The bundle does not state active exploitation, and KEV is false. The CVSS vector requires user interaction, consistent with a CSRF-driven attack where a privileged user is induced to perform an unsafe action.
Researcher notes
The public bundle identifies the weakness and impact but does not include exploit details, a fixed version, or confirmed exploitation. Validation should focus on plugin presence, version, advisory status, and evidence of unexpected stored content changes.
Mitigation direction
- Inventory WordPress sites for The Visitor Counter plugin versions 1.4.3 or earlier.
- Check vendor, WordPress.org, or Patchstack guidance for a fixed release or official remediation.
- Update to a vendor-identified fixed version if one is available.
- If no fixed version is available, assess disabling or removing the plugin.
- Restrict administrative access and reinforce anti-phishing controls for WordPress administrators.
Validation and detection
- Confirm whether each WordPress site has The Visitor Counter plugin installed.
- Record installed plugin versions and flag 1.4.3 or earlier for review.
- Review vendor and Patchstack advisories for current fix status.
- Inspect WordPress admin activity and content changes for unexpected stored script indicators.
- Verify any remediation in a staging environment before production rollout.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-2025-31449 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.