CVE-2025-13753

WP Table Builder <= 2.0.19 - Incorrect Authorization to Authenticated (Subscriber+) Arbitrary Table Creation

2026-01-08 18:58
Dmitrii Ignatyev

Strategic Overview

Status
Patched in 2.0.20
Affected Plugin
WP Table Builder – Drag & Drop Table Builder
Affected Version
<= 2.0.19
CVSS
4.3Medium
Weakness type
CWE-863 · Incorrect Authorization
CVE
CVE-2025-13753
View all WP Table Builder – Drag & Drop Table Builder vulnerabilities

At a glance

CVE-2025-13753 is a medium-severity Incorrect Authorization vulnerability in the WP Table Builder WordPress plugin, affecting versions <= 2.0.19. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.0.20; sites on affected versions should update now. Disclosed January 2026, reported by Dmitrii Ignatyev.

Vulnerability Overview

The WP Table Builder – Drag & Drop Table Builder plugin for WordPress is vulnerable to unauthorized modification of data due to an incorrect authorization check on the save_table() function in all versions up to, and including, 2.0.19. This makes it possible for authenticated attackers, with Subscriber-level access and above, to create new wptb-table posts.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-863: Incorrect Authorization

WP Table Builder <= 2.0.19 carries this weakness at save_table(), and reaching it takes an account at Subscriber level or above. Incorrect authorization means a permission check exists but evaluates the wrong thing, so it passes for callers it was meant to stop.

The action runs for users the code intended to exclude, with the same effect as having no check at all. For WP Table Builder the fix is 2.0.20: builds <= 2.0.19 are affected, anything from 2.0.20 onward is not.

Remediation

Update to version 2.0.20, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WP Table Builder 2.0.20 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-13753https://www.wordfence.com/threat-intel/vulnerabilities/id/95f49080-2263-4f6d-9372-30137efd8e10https://nvd.nist.gov/vuln/detail/CVE-2025-13753

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C