Skip to main content
Menu
CVEs

Toocheke Companion arbitrary post deletion via AJAX handler

CVE-2026-120556Published , updated

8.1HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

The Toocheke Companion plugin for WordPress lets a logged-in user with Contributor-level access or higher permanently delete series posts, their child comic posts, and related Media Library attachments, even when other users created them. The attack can be carried out remotely over the network because the plugin's AJAX handlers skip the per-post ownership check.

Written by a model

Original description

The Toocheke Companion plugin for WordPress is vulnerable to Missing Authorization leading to arbitrary post and attachment deletion in versions up to, and including, 2.38. This is due to a missing object-level capability check in the toocheke_tapas_ajax_cleanup_start() and toocheke_tapas_ajax_cleanup_step() AJAX handlers; the toocheke_tapas_cleanup_ajax_guard() method only verifies the primitive delete_posts capability (held by every Contributor) and never calls current_user_can('delete_post', $post_id) or delete_others_posts before passing the attacker-supplied series_post_id to wp_delete_post() and wp_delete_attachment() with force-delete enabled. The required nonce is emitted on the Import: Tapas admin page, which is gated only by edit_posts, so a Contributor can read it. This makes it possible for authenticated attackers, with Contributor-level access and above, to permanently delete any importer-created series post, every child 'comic' post attached to it, and every Media Library attachment belonging to those posts — regardless of which user originally created them.

What to do

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-120556 (Toocheke Companion <= 2.38 - Missing Authorization to Authenticated (Contributor+) Arbitrary Post Deletion via 'series_post_id' Parameter), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-120556 (entry last updated 2026-11-20):
Affected:
- toocheke Toocheke Companion: through 2.38
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-120556 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-120556 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/545eee3c-608a-4275-b533-c67e420baeb3?source=cve
- https://plugins.trac.wordpress.org/browser/toocheke-companion/tags/2.37/inc/class-toocheke-companion-import-tapas.php#L679
- https://plugins.trac.wordpress.org/browser/toocheke-companion/tags/2.37/inc/class-toocheke-companion-import-tapas.php#L693
- https://plugins.trac.wordpress.org/browser/toocheke-companion/tags/2.37/inc/class-toocheke-companion-import-tapas.php#L674
- https://plugins.trac.wordpress.org/browser/toocheke-companion/tags/2.37/inc/class-toocheke-companion-import-tapas.php#L604
- https://plugins.trac.wordpress.org/browser/toocheke-companion/tags/2.37/inc/class-toocheke-companion-import-tapas.php#L558
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3811834%40toocheke-companion&new=3811834%40toocheke-companion
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-120556
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-120556"}.

Affected versions

cve.now Index

16Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.1/10CVSS 8.1
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 71 if added to CISA KEV
  • Would score about 66 if CISA's SSVC rates exploitation active
  • Would score about 35 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 8

Questions about CVE-2026-120556

Is CVE-2026-120556 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-120556?

Toocheke Companion: through 2.38.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.