CVE Intelligence
Skip to main content
highAccess Controlpublic exploit

CVE-2026-6922

CVE-2026-6922 — WP Table Builder <= 2.2.1 - Incorrect Authorization to Authenticated (Subscriber+) Arbitrary Post Deletion via 'ids' Parameter

The WP Table Builder – Drag & Drop Table Builder plugin for WordPress is vulnerable to Incorrect Authorization in all versions up to, and including, 2.2.1. This is due to an operator precedence bug in the post-type guard within the trash_table_bulk() and restore_table_bulk() functions that causes the guard to never fire, combined with a permission callback that only verifies plugin role membership without per-post-type or ownership checks. This makes it possible for authenticated attackers, with subscriber-level access and above, to trash or restore any post, page, or custom post type on the site by supplying arbitrary post IDs.

Published Updated Sources: NVD, wptb (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

0%

ahead of 0% of scored CVEs

Affects

wptb

WP Table Builder – Drag & Drop Table Builder

CVSS base

7.1

high

Remediation

The vendor's own words where we have them.

Upgrade WP Table Builder – Drag & Drop Table Builder to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

  • Identify exposed assets running affected vendor/product/version combinations.
  • Prioritize based on EPSS, PoC availability, and external exposure.
  • Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

VendorProductVersionsStatus
wptbWP Table Builder – Drag & Drop Table Builder0 to <= 2.2.1Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

None

Integrity

Low

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

Low

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
7.1CVSS 3.1high2.84.2NVD, wptb (CNA), GHSA

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-863 · Incorrect Authorization

  • Read Application Data
  • Read Files or Directories
  • Modify Application Data
  • Modify Files or Directories

Mitigation: Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.

Weakness & attack patterns

  • CWE-863Incorrect Authorization

Inferred from the weakness class — not observed against this CVE.

CAPEC-1 · Accessing Functionality Not Properly Constrained by ACLsCAPEC-122 · Privilege Abuse

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

4

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Prioritize edge telemetry for network-reachable WP Table Builder – Drag & Drop Table Builder.
  • Monitor for scanner or exploit-pattern traffic after 4 public PoC repositories were reported.
web/proxy/WAF logsapplication logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

  1. 2026

  2. Added · CVSS 3.1 7.1 (AV:N)

    Sep 22, 2026 · NVD

  3. Initial · CVE published

    Sep 22, 2026 · NVD

  4. Added · GHSA-v8f2-9v32-fmmf published (high)

    Sep 22, 2026 · GitHub Security Advisory

  5. CVE published by MITRE.

    Sep 22, 2026 · SOCRadar CTI

  6. Reported · Disclosed

    Sep 21, 2026 · wptb

  7. Reported · Vendor Notified

    Apr 23, 2026 · wptb

Source activity

Readings a source repeats on a schedule, counted rather than listed.

  • 1×2 times mentioned on 1 Telegram channelsSep 22, 2026 · SOCRadar CTI

References

14 on the record

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1

What should defenders know first?

CVE-2026-6922 is WP Table Builder <= 2.2.1 - Incorrect Authorization to Authenticated (Subscriber+) Arbitrary Post Deletion via 'ids' Parameter, a high vulnerability affecting WP Table Builder – Drag & Drop Table Builder from wptb. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-6922. Public exploit evidence is: 4 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.1 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.