LiveActive security incident?Get immediate response
CVE Record

CVE-2022-4541: WordPress Visitors <= 1.0 - Unauthenticated Stored Cross-Site Scripting via HTTP Header

The WordPress Visitors plugin for WordPress is vulnerable to Stored Cross-Site Scripting via a spoofed HTTP Header value in versions up to, and including, 1.0 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses the nm_vistior page.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A vulnerable WordPress Visitors plugin can let an unauthenticated visitor store script content through a spoofed HTTP header. That script can later run when someone views the plugin’s visitor page, creating risk to administrator sessions and site integrity.

Executive priority

Treat as a high-priority WordPress plugin exposure where the plugin is present. The main business risk is compromise of privileged browser sessions or administrative actions through stored script execution.

Technical view

CVE-2022-4541 is stored cross-site scripting in WordPress Visitors versions up to and including 1.0. The source attributes the flaw to insufficient sanitization and output escaping of an HTTP header value displayed on the nm_vistior page. CWE-79 applies; CVSS is 7.2 high.

Likely exposure

Exposure is limited to WordPress sites running the WordPress Visitors plugin at affected versions through 1.0. Risk is higher where privileged users access the plugin’s visitor reporting page.

Exploitation context

The source states unauthenticated attackers can inject arbitrary web scripts through a spoofed HTTP header. The bundle does not cite CISA KEV listing or other evidence of active exploitation.

Researcher notes

Evidence is narrow but consistent: the CVE description, Wordfence reference, and plugin source references point to header data stored and rendered without sufficient sanitization or escaping. No exploit-in-the-wild evidence is provided in the bundle.

Mitigation direction

  • Inventory WordPress sites for the WordPress Visitors plugin and installed version.
  • Check vendor or Wordfence guidance for a fixed version or official remediation.
  • If no safe fixed release is available, disable or remove the plugin.
  • Review affected sites for suspicious visitor records or unexpected script content.
  • Limit access to WordPress administration and monitoring pages to trusted users.

Validation and detection

  • Confirm whether the WordPress Visitors plugin is installed on each WordPress site.
  • Verify the installed plugin version is not affected through version 1.0.
  • Inspect the visitor page output for unescaped header-derived content.
  • Review web and application logs for suspicious header values.
  • Check whether administrators recently accessed the affected visitor page.
Prepared
Confidence
high
Sources
5

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-4541 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
High
CVSS
7.2 (3.1)
Known Exploited
No
Published

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

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
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N3.92.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.2High
CVSS 3.1 vector shape for CVE-2022-4541Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
nitinmaurya12WordPress Visitors0unaffected
Weakness

CWE details

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.