# CVE-2026-14924: Tablesome < 1.1.31 - Unauthenticated Post Creation and Modification

> Unauthenticated attackers can create new posts and overwrite existing pages due to missing authorization checks in the Tablesome WordPress plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jul 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-jc98-p7c8-r93j

## What is CVE-2026-14924?

CVE-2026-14924 is a high-severity missing authorization vulnerability in Unknown Tablesome Table, published on 28 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Tablesome Table  WordPress plugin before 1.1.31 does not perform any authentication, capability, or nonce checks in one of its AJAX actions, allowing unauthenticated users to create new published posts and to overwrite arbitrary existing posts and pages.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-14924?


## How do I fix CVE-2026-14924?

No fix has been published for CVE-2026-14924 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-14924 being exploited?

There is no known exploitation of CVE-2026-14924 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-14924 and fix it if it is affected.

What it is: CVE-2026-14924 is a high-severity missing authorization vulnerability in Unknown Tablesome Table, published on 28 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14924 in the wild and no public exploit code.

Affected product: Unknown Tablesome Table. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-14924/ (Markdown: https://insights.sbomify.com/CVE-2026-14924/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-14924
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-14924
- OSV: https://osv.dev/vulnerability/CVE-2026-14924

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-14924/
Summaries are generated and may contain mistakes; the official description above is the record.