LiveActive security incident?Get immediate response
CVE Record

CVE-2022-25601: WordPress Contact Form X plugin <= 2.4 - Reflected Cross-Site Scripting (XSS) vulnerability

Reflected Cross-Site Scripting (XSS) vulnerability affecting parameter &tab discovered in Contact Form X WordPress plugin (versions <= 2.4).

MediumCVSS 4.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-25601 is a reflected XSS issue in the Contact Form X WordPress plugin through version 2.4. A victim must interact with a crafted link or request. Business impact is mainly limited unauthorized page manipulation in the victim’s browser, not direct server takeover based on the supplied evidence.

Executive priority

Treat as a scheduled remediation item for affected WordPress sites, not an emergency based on current evidence. Prioritize public-facing or administrator-heavy sites because exploitation depends on tricking a user into interacting with malicious content.

Technical view

The issue is CWE-79 reflected cross-site scripting involving the tab parameter in Contact Form X <= 2.4. CVSS 3.1 is 4.7 with network attack vector, low complexity, user interaction required, changed scope, no confidentiality impact, low integrity impact, and no availability impact.

Likely exposure

Exposure is limited to WordPress sites running Jeff Starr’s Contact Form X plugin at version 2.4 or earlier. The bundle does not identify affected CPEs or confirm whether later plugin versions contain a fix.

Exploitation context

The CVE is not listed as KEV in the supplied bundle, and no cited source states active exploitation. Exploitation requires user interaction. One reference title calls it authenticated XSS, while the CVSS vector says no privileges required, so access requirements should be verified.

Researcher notes

Evidence supports reflected XSS in the tab parameter, but source details are thin. The authentication requirement is inconsistent between the Patchstack reference title and the CVSS vector. Do not assume exploitation in the wild or a fixed version without checking the linked vendor records.

Mitigation direction

  • Inventory WordPress sites for Contact Form X versions 2.4 or earlier.
  • Check WordPress plugin and Patchstack guidance for a fixed or safe version.
  • Update the plugin if vendor guidance confirms a patched release.
  • Disable or remove the plugin where no safe update path exists.
  • Warn administrators not to follow untrusted Contact Form X links.

Validation and detection

  • Confirm whether Contact Form X is installed on each WordPress site.
  • Record the installed plugin version and compare it with <= 2.4 exposure.
  • Review plugin changelog or vendor guidance for the fix status.
  • Check logs for suspicious requests involving the tab parameter.
  • Validate that remediation removes or upgrades vulnerable installations.
Prepared
Confidence
medium
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-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-25601 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
4.7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/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
6Source 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
4.7CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N2.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Jeff StarrContact Form X (WordPress plugin)<= 2.4Listed
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.