LiveActive security incident?Get immediate response
CVE Record

CVE-2022-45825: WordPress WPComplete Plugin <= 2.9.4 is vulnerable to Cross Site Scripting (XSS)

Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in iThemes WPComplete plugin <= 2.9.2 versions.

HighCVSS 7.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-45825 is a reflected cross-site scripting issue in the iThemes WPComplete WordPress plugin. A successful attack would require a user to interact with attacker-controlled content, but it could still affect site users or administrators through browser-executed script.

Executive priority

Prioritize this for WordPress estates that run WPComplete, especially sites with administrator traffic. It is not confirmed as actively exploited in the provided sources, but the unauthenticated and public-web nature makes timely validation appropriate.

Technical view

The bundle describes unauthenticated reflected XSS, CWE-79, in WPComplete. CVSS 3.1 is 7.1 with network access, low complexity, no privileges required, user interaction required, changed scope, and low confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely on public WordPress sites using the WPComplete plugin. The source bundle is inconsistent on affected versions, naming <=2.9.2 in the description and <=2.9.4 in the title, so version validation needs vendor confirmation.

Exploitation context

The bundle does not show CISA KEV listing or other cited evidence of active exploitation. Because exploitation requires user interaction, realistic risk depends on whether attackers can get users or administrators to open crafted links or content.

Researcher notes

Key uncertainty is the affected range: the title says <=2.9.4 while the description says <=2.9.2. Do not assume exploitability or fixed status from the bundle alone; confirm with vendor/Patchstack records and local plugin versions.

Mitigation direction

  • Identify WordPress sites running the WPComplete plugin.
  • Compare installed versions against CVE and Patchstack guidance.
  • Update or remove WPComplete if a vulnerable version is present.
  • Check iThemes or Patchstack for fixed-release guidance.
  • Use WAF controls only as temporary risk reduction.

Validation and detection

  • Inventory WPComplete presence and versions across WordPress sites.
  • Confirm whether the plugin is active on internet-facing sites.
  • Review vendor and Patchstack records for affected-version clarification.
  • Check logs for suspicious requests targeting WPComplete paths.
  • Validate remediation by confirming the plugin is updated or removed.
Prepared
Confidence
medium
Sources
3

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-45825 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.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

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
2Source 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.1CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L2.83.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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