LiveActive security incident?Get immediate response
CVE Record

CVE-2022-34650: WordPress Team plugin <= 1.2.6 - Multiple Authenticated Stored Cross-Site Scripting (XSS) vulnerabilities

Multiple Authenticated (contributor or higher user role) Stored Cross-Site Scripting (XSS) vulnerabilities in wpWax Team plugin <= 1.2.6 at WordPress.

MediumCVSS 4.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-34650 affects the wpWax Team WordPress plugin through version 1.2.6. A logged-in user with contributor or higher privileges could store malicious script content that runs when another user views affected content. Business risk is moderate because exploitation requires an authenticated account and user interaction, but it can still alter page behavior or abuse admin trust.

Executive priority

Treat this as a moderate-priority WordPress hygiene issue. It is unlikely to be an unauthenticated mass-compromise path from the provided evidence, but it can create trust and integrity risk on sites with many content contributors.

Technical view

The issue is multiple authenticated stored XSS vulnerabilities in the Team plugin for WordPress, tracked as CWE-79. The CVSS 3.1 score is 4.1 with low attack complexity, low privileges required, required user interaction, changed scope, and low integrity impact. Sources identify affected versions as <= 1.2.6 but do not state a fixed version.

Likely exposure

Exposure is limited to WordPress sites running the wpWax Team plugin at version 1.2.6 or earlier, especially where contributor-level users or higher can create or edit affected plugin content.

Exploitation context

The source bundle does not indicate known active exploitation, and the CVE is not listed as KEV. Exploitation requires authenticated access and another user viewing the stored content, so shared editorial environments carry more practical risk.

Researcher notes

The available evidence identifies authenticated stored XSS and affected versions, but not the vulnerable parameters, fixed version, or exploit telemetry. Do not assume active exploitation or a specific patch level beyond checking current vendor guidance.

Mitigation direction

  • Check vendor and WordPress plugin guidance for a fixed release.
  • Update the Team plugin if a safe newer version is available.
  • Disable or remove the plugin if it is unused.
  • Restrict contributor-level access on affected WordPress sites.
  • Review untrusted Team plugin content created by non-admin users.

Validation and detection

  • Inventory WordPress sites for the adl-team or Team plugin.
  • Confirm whether installed plugin versions are <= 1.2.6.
  • Review contributor, author, editor, and administrator account access.
  • Check affected pages for unexpected script-like content.
  • Document remediation status for each affected site.
Prepared
Confidence
medium
Sources
4

Public sources used

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-34650 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.1 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:L/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
wpWaxTeam (WordPress plugin)<= 1.2.6Listed
Weakness

CWE details

CWE-79

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.