Toocheke Companion stored XSS via meta value parameter
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
The Toocheke Companion plugin for WordPress has a stored cross-site scripting flaw that lets an attacker with author-level access or higher inject malicious scripts into pages. The attacker can reach it remotely over the network with a low-privilege login, and the scripts run whenever a user opens the injected page.
Written by a model
Original description
The Toocheke Companion plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'meta[<meta_id>][value]' parameter in all versions up to, and including, 2.39 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with author-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is possible because omitting the comic_blog_post_editor field from the POST request bypasses the plugin's sanitization callback entirely, causing WordPress core to store the raw payload byte-for-byte via update_post_meta().
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-120494 (Toocheke Companion <= 2.39 - Authenticated (Author+) Stored Cross-Site Scripting via 'meta[][value]' 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-120494 (entry last updated 2026-11-20):
Affected:
- toocheke Toocheke Companion: through 2.39
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-120494 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-120494 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/b4bd9d3a-0706-4087-8c28-597b959aec4d?source=cve
- https://plugins.trac.wordpress.org/browser/toocheke-companion/tags/2.38/templates/content-comicblogpost.php#L41
- https://plugins.trac.wordpress.org/browser/toocheke-companion/tags/2.38/templates/content-comicblogpost.php#L45
- https://plugins.trac.wordpress.org/browser/toocheke-companion/tags/2.38/inc/class-toocheke-companion-metaboxes.php#L197
- https://plugins.trac.wordpress.org/browser/toocheke-companion/tags/2.38/inc/class-toocheke-companion-cpt-taxonomy.php#L148
- https://wordpress.org/plugins/toocheke-companion/
- https://plugins.trac.wordpress.org/changeset/3811901/toocheke-companion/trunk/templates/content-comicblogpost.php
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-120494
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-120494"}.Affected versions
- toocheke Toocheke Companionthrough 2.39
cve.now Index
- 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
- Severity6.4/10CVSS 6.4
- No patch5/5No patch listed yet
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 33 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 8
Questions about CVE-2026-120494
Is CVE-2026-120494 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-120494?
Toocheke Companion: through 2.39.
Source: cve.now feed data
Related
- CVE-2026-120556Toocheke Companion <= 2.38 - Missing Authorization to Authenticated (Contributor+) Arbitrary Post Deletion via 'series_post_id' Parameter
- CVE-2026-32403WordPress Toocheke Companion plugin <= 1.194 - Cross Site Scripting (XSS) vulnerability
- CVE-2026-15604Toocheke Companion <= 2.10 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'series_bg_color' Post Meta
- CVE-2025-23992WordPress Toocheke Companion plugin <= 1.166 - Stored Cross Site Scripting (XSS) vulnerability
- CVE-2026-129327Apaczka.pl WooCommerce <= 1.4.8 - Unauthenticated Stored Cross-Site Scripting via '_apaczka' Parameter via Guest Checkout
- CVE-2026-131582PagBank / PagSeguro e Vindi para WooCommerce <= 5.1.6 - Unauthenticated Stored Cross-Site Scripting via 'customer.name' Parameter
No corrections so far. Something wrong on this page? Report an error.