Ninja TablesWordPress extension · Wpmanageninja
CVE-2025-2939
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 · uneditedThe Ninja Tables – Easy Data Table Builder plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 5.0.18 via deserialization of untrusted input from the args[callback] parameter . This makes it possible for unauthenticated attackers to inject a PHP Object. The additional presence of a POP chain allows attackers to execute arbitrary functions, though it does not allow user supplied parameters only single functions can be called so the impact is limited.
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 confidenceThe Ninja Tables WordPress plugin up to version 5.0.18 is vulnerable to PHP Object Injection via deserialization of untrusted input from the args[callback] parameter. While unauthenticated attackers can inject PHP objects and leverage a POP chain to call arbitrary functions, the restriction that user-supplied parameters cannot be passed limits the exploitation potential.
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
Ninja TablesWordPress extension
< 5.0.19CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/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.
-
Check Ninja Tables plugin version in WordPress adminGo to WordPress dashboard > Plugins > Installed Plugins. Locate 'Ninja Tables' in the list and read the version number displayed beneath the plugin name.Affected if Version shown is lower than 5.0.19 (for example, 5.0.18, 5.0.17, etc.)
-
Verify version via plugin main fileAccess the file /wp-content/plugins/ninja-tables/ninja-tables.php via FTP, file manager, or WP-CLI. Open the file and find the 'Version:' field in the plugin header comment at the top.Affected if The Version field shows a number less than 5.0.19
-
Query plugin version via WP-CLIRun the command 'wp plugin list --name=ninja-tables' if WP-CLI is available on the server. The output will show the installed version.Affected if The version column shows anything below 5.0.19
You are affected if the installed Ninja Tables plugin version is any version below 5.0.19.
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.
dbcve · scoped5.0.19
Update Ninja Tables plugin to version 5.0.19 or later to patch the deserialization vulnerability.
Ninja Tables 5.0.19
- Back up your WordPress site before making any changes
- Navigate to Plugins > Installed Plugins in WordPress admin
- Find Ninja Tables in the plugin list
- Click 'Update now' if an update is available, or manually upload version 5.0.19
- Verify the plugin is updated to version 5.0.19 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ninja Tables
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2939 — 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-2025-2939 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