LiveActive security incident?Get immediate response
CVE Record

CVE-2022-40131: WordPress Page View Count plugin <= 2.5.5 - Cross-Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in a3rev Software Page View Count plugin <= 2.5.5 on WordPress allows an attacker to reset the plugin settings.

MediumCVSS 5.4Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This vulnerability affects the Page View Count WordPress plugin at versions 2.5.5 and earlier. A malicious site could trick a logged-in WordPress administrator into causing the plugin settings to be reset. The known impact is limited to integrity and availability of plugin configuration, not site takeover or data theft.

Executive priority

Treat this as a moderate WordPress hygiene issue. It is not evidenced as actively exploited, but affected sites should be found and remediated during normal patch cycles because administrator interaction could disrupt plugin configuration.

Technical view

CVE-2022-40131 is a CSRF issue in a3rev Software Page View Count for WordPress. The source bundle states affected versions are <= 2.5.5 and that exploitation can reset plugin settings. CVSS 3.1 is 5.4 with network access, low complexity, no attacker privileges, and required user interaction.

Likely exposure

Exposure is likely limited to WordPress sites running Page View Count version 2.5.5 or earlier, especially where administrators are active in the dashboard.

Exploitation context

The bundle does not show KEV listing or active exploitation evidence. Exploitation requires user interaction, consistent with CSRF, likely involving a logged-in administrator being induced to take an unsafe browser action.

Researcher notes

The public bundle is sparse: it identifies CSRF, affected versions, CVSS, and reset-settings impact, but does not include exploit details, proof of exploitation, or explicit remediation text. Avoid asserting broader WordPress compromise without additional evidence.

Mitigation direction

  • Inventory WordPress sites for the Page View Count plugin and installed version.
  • Check Patchstack and the WordPress plugin changelog for vendor-fixed versions or guidance.
  • Update the plugin if vendor guidance identifies a safe release.
  • Disable or remove the plugin if it is unnecessary or cannot be safely updated.
  • Limit WordPress administrator browsing from active authenticated sessions where practical.

Validation and detection

  • Confirm whether Page View Count is installed on each WordPress site.
  • Record installed versions and flag any version <= 2.5.5.
  • Verify vendor guidance before marking a later version remediated.
  • Review administrative change history for unexpected plugin setting resets.
  • Confirm remediation in staging before broad production rollout.
Prepared
Confidence
high
Sources
4

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-40131 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.4 (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:L

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
5.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L2.82.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.4Medium
CVSS 3.1 vector shape for CVE-2022-40131Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
a3rev SoftwarePage View Count (WordPress plugin)<= 2.5.5Listed
Weakness

CWE details

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.