dbcve.org
Wp Table ManagerWordPress extension · Joomunited

CVE-2022-47602

MEDIUM · 5.4 CVSS v3.1 Published 2023-03-29
Fix available
A fix is available. Upgrade to after 3.5.2 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
Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in JoomUnited WP Table Manager plugin <= 3.5.2 versions.

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 confidence

Stored Cross-Site Scripting (XSS) vulnerability in JoomUnited WP Table Manager plugin allows authenticated users with contributor role or higher to inject malicious scripts that persist in the database and execute when other users view affected table content.

MitigationUpdate WP Table Manager plugin to version greater than 3.5.2 once patched; until then, restrict user permissions to contributor+ roles or implement WAF/Content-Security-Policy headers as compensating controls.

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
Wp Table ManagerWordPress extension
Affected:<= 3.5.2

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. Verify WP Table Manager plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Table Manager' or check the /wp-content/plugins/wp-table-manager/ directory exists
    Affected if Plugin is installed and active
  2. Check installed plugin version
    Navigate to Plugins > Installed Plugins > WP Table Manager, or inspect the main plugin file header for 'Version:' value
    Affected if Version is 3.5.2 or lower (any version <= 3.5.2)
  3. Identify users with contributor role or higher
    Go to Users > All Users in WordPress admin and filter by roles: Administrator, Editor, Author, Contributor
    Affected if Any user account with contributor role or higher exists on the site
  4. Confirm table data storage
    Check if any tables have been created in WP Table Manager by accessing the plugin and viewing saved tables, or query the wp_options table for 'wptm_tables' option
    Affected if At least one table has been created and saved in the plugin

User is affected if WP Table Manager plugin version 3.5.2 or lower is installed, there are users with contributor+ permissions, and tables have been created in the plugin.

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.

From vendor data
Upgrade available Upgrade to a release after 3.5.2
Interim mitigation

Update WP Table Manager plugin to version greater than 3.5.2 once patched; until then, restrict user permissions to contributor+ roles or implement WAF/Content-Security-Policy headers as compensating controls.

Fix this in Wp Table Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-47602 — 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-47602 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