Security readout for executives and security teams
Plain-English summary
This affects a WordPress hit-counter plugin, not WordPress core. A malicious site could trick a logged-in user into making an unintended plugin-related change. The cited severity is medium, with low integrity impact and no confidentiality or availability impact listed.
Executive priority
Treat as a routine medium-priority WordPress plugin remediation. It is not supported by the provided sources as actively exploited, but exposed WordPress plugins can create avoidable operational risk if left untracked or unmaintained.
Technical view
CVE-2023-46087 is a CWE-352 CSRF issue in Mahlamusa Who Hit The Page - Hit Counter plugin versions <= 1.4.14.3. CVSS 3.1 is 4.3: network-reachable, low complexity, no attacker privileges, user interaction required, unchanged scope, low integrity impact.
Likely exposure
Exposure is limited to WordPress sites running the who-hit-the-page-hit-counter plugin at version 1.4.14.3 or earlier. The bundle does not identify affected configuration details, installed-base scale, or whether unauthenticated visitors can reach the vulnerable workflow.
Exploitation context
The source bundle does not show active exploitation, and CISA KEV is false. Exploitation would require user interaction, typically a logged-in WordPress user visiting attacker-controlled content, but the public bundle does not describe the exact affected action.
Researcher notes
Evidence is sparse. The bundle names CSRF, affected versions <= 1.4.14.3, CVSS 4.3, CWE-352, and Patchstack as the VDB source. It does not name the vulnerable endpoint, nonce failure details, fixed version, or proof-of-concept status.
Mitigation direction
- Inventory WordPress sites for the who-hit-the-page-hit-counter plugin.
- Check installed versions and flag 1.4.14.3 or earlier.
- Consult vendor, WordPress plugin, or Patchstack guidance for a fixed release.
- Disable or remove the plugin where no maintained fix is available.
- Prioritize sites with administrative users and public internet exposure.
Validation and detection
- Confirm plugin package name is who-hit-the-page-hit-counter.
- Record installed plugin version from each WordPress instance.
- Verify whether sites still require this plugin's functionality.
- Check security monitoring for unexpected plugin setting changes.
- Document remediation decision and remaining accepted risk.
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-2023-46087 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
- Medium
- CVSS
- 4.3 (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:N
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:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Source materials
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.