dbcve.org
TeamWordPress extension · Wpwax

CVE-2022-34853

MEDIUM · 5.4 CVSS v3.1 Published 2022-07-22
Fix available
A fix is available. Upgrade to after 1.2.6 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Authenticated persistent XSS vulnerabilities in wpWax Team plugin <= 1.2.6 allow contributor-level or higher users to inject malicious scripts that execute when other users view the affected team member entries. The stored nature means the malicious payload persists in the database.

MitigationUpdate wpWax Team plugin to latest version beyond 1.2.6; if unavailable, disable the plugin. Apply output encoding and input sanitization using WordPress sanitization functions (sanitize_text_field, esc_html, etc.) on all user-supplied fields.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TeamWordPress extension
Affected:<= 1.2.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if wpWax Team plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'wpWax Team' in the list. Note the version number displayed next to the plugin name.
    Affected if The plugin is installed and the version shown is 1.2.6 or lower
  2. Verify the plugin version number
    Click on the plugin name in the plugins list to view details, or check the plugin's main PHP file header for the 'Version' comment. Compare the version against the affected range: <=1.2.6
    Affected if Version is 1.2.6 or any version number lower than 1.2.6
  3. Confirm the plugin is active
    In Plugins > Installed Plugins, check if wpWax Team has an 'Active' status under the plugin name.
    Affected if Plugin is currently active and the version is <=1.2.6
  4. Inspect team member entries for suspicious scripts
    Go to the Team section in WordPress admin (the plugin adds a Team or wpWax Team menu item). Review each team member entry for any unexpected script tags, event handlers (onclick, onerror, onload), or encoded JavaScript in text fields such as name, bio, or custom fields.
    Affected if Any team member entries contain script tags, JavaScript event handlers, or suspicious encoded content that could indicate a stored XSS payload

You are affected if wpWax Team plugin is installed with version 1.2.6 or lower and the plugin is active, particularly if untrusted users with contributor-level or higher access can modify team member entries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 1.2.6
Interim mitigation

Update wpWax Team plugin to latest version beyond 1.2.6; if unavailable, disable the plugin. Apply output encoding and input sanitization using WordPress sanitization functions (sanitize_text_field, esc_html, etc.) on all user-supplied fields.

Recommended fix Moderate confidence

Team plugin version 1.2.7 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the wpWax Team plugin
  4. Check if an update is available and update to the latest version (version 1.2.7 or higher)
  5. Alternatively, download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Team Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34853 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-34853 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data