CVE-2022-47601
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 · uneditedMissing Authorization vulnerability in JoomUnited WP Table Manager allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WP Table Manager: from n/a through 3.5.2.
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 confidenceMissing Authorization vulnerability in the WP Table Manager plugin allows attackers to access functionality they shouldn't have permission to use due to incorrectly configured access control security levels. Unauthenticated or unauthorized users can exploit this to perform privileged operations or access sensitive data that should be restricted to administrative users.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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 WP Table Manager plugin is installedLog in to WordPress admin panel and navigate to Plugins > Installed Plugins. Look for WP Table Manager in the list of active plugins.Affected if The plugin is installed and active on the WordPress site
-
Check installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins. Click on the View Details link for WP Table Manager to see the installed version number.Affected if Plugin version is displayed and can be compared to the fixed release
-
Compare version to fixed releaseCompare the installed version to version 3.5.3. Versions prior to 3.5.3 are affected by the missing authorization vulnerability.Affected if Installed version is earlier than 3.5.3
-
Test unauthorized access to plugin functionsAttempt to access WP Table Manager admin pages (typically under /wp-admin/admin.php?page=wp-table-manager*) while logged out or as a non-administrator user. If access is granted without proper authentication, the vulnerability is present.Affected if Unauthenticated or unauthorized access to plugin administrative functions is possible
If WP Table Manager is installed with a version earlier than 3.5.3 and allows unauthenticated or unauthorized users to access administrative functions or data, the environment is affected by CVE-2022-47601.
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 WP Table Manager to version 3.5.3 or later which contains proper authorization controls. As a temporary measure, restrict access to wp-admin and plugin admin pages using web server-level authentication or IP allow-listing.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47601 — 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-47601 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