TeamWordPress extension · Wpwax
CVE-2022-34650
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 · uneditedMultiple Authenticated (contributor or higher user role) Stored 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 · moderate confidenceThe wpWax Team plugin for WordPress versions 1.2.6 and below contains multiple stored XSS vulnerabilities. Authenticated users with contributor or higher roles can inject malicious JavaScript into plugin fields (likely team member profile data such as name, bio, or image captions). This payload persists on the server and executes in the browsers of other users and site visitors who view the affected team pages.
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
<= 1.2.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify wpWax Team plugin is installedLog into WordPress admin, go to Plugins > Installed Plugins, and look for 'wpWax Team' in the list. Alternatively, use WP-CLI: wp plugin list --name='wpwax-team'Affected if The plugin is installed and shows version 1.2.6 or lower in the version column
-
Confirm the installed version numberIn the WordPress admin Plugins page, click on the plugin name to view details, or check the plugin header in wp-content/plugins/wpwax-team/main-plugin-file.php. With WP-CLI: wp plugin get wpwax-teamAffected if The displayed version is 1.2.6 or any version lower than that
-
Identify stored team member dataAccess your WordPress database via phpMyAdmin or mysql command line. Look for post type entries created by the plugin (commonly named 'team' or 'team_member' in wp_posts) and their metadata in wp_postmeta. With WP-CLI: wp post list --post_type=teamAffected if There are team member posts present in the database
-
Inspect team fields for malicious scriptsExamine the team member entries for unsanitized content in fields such as member name, bio/description, position/title, or image caption. Query the database directly or view the team page on your site and inspect the HTML source for <script> tags, javascript: URIs, or event handlers like onload/onerrorAffected if Any team member data contains raw HTML, script tags, or JavaScript event handlers that should not be there
-
Audit user accounts with contributor accessIn WordPress admin, go to Users > All Users and review the role column. Users with Contributor, Author, Editor, or Administrator roles could have exploited this vulnerability. With WP-CLI: wp user list --role=contributorAffected if There are one or more users with contributor-level or higher access who could have injected the malicious payload
You are affected if the wpWax Team plugin version is 1.2.6 or lower AND there are team member entries in your database containing unsanitized HTML or JavaScript code.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate the wpWax Team plugin to the latest version beyond 1.2.6. If no update is available, disable or remove the plugin until a patch is released.
Fix this in Team
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34650 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-34650 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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