CVE
Custom Twitter Feeds unauthenticated stored XSS via feed parameter
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
The Custom Twitter Feeds – A Tweets Widget or X Feed Widget plugin for WordPress lets unauthenticated attackers remotely, without logging in, store malicious scripts through its feed parameter. The scripts run in a page when a user opens the injected page, and they are later saved by a scheduled update job so that they run when an administrator loads the Support page.
Original description
The Custom Twitter Feeds – A Tweets Widget or X Feed Widget plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'atts (JSON object, specifically the inner feed key)' parameter in all versions up to, and including, 2.11.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The injected payload is first stored in the wp_ctf_feed_caches database table and later written into the ctf_cron_report WordPress option by the scheduled ctf_feed_update cron job, meaning execution is deferred until the cron runs and an administrator subsequently loads the Support page.
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.2/10CVSS 7.2
- No patch5/5No patch listed yet
What would change the score
- Would score about 74 if added to CISA KEV
- Would score about 69 if CISA's SSVC rates exploitation active
- Would score about 34 if advisories confirm default setups are exposed
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-116536 (Custom Twitter Feeds <= 2.11.1 - Unauthenticated Stored Cross-Site Scripting via 'atts[feed]' 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-116536 (entry last updated 2026-11-18):
Affected:
- smub Custom Twitter Feeds – A Tweets Widget or X Feed Widget: through 2.11.1
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-116536 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-116536 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/03101d34-112b-4508-9aca-ade87c7a8853?source=cve
- https://plugins.trac.wordpress.org/browser/custom-twitter-feeds/tags/2.10.0/inc/Admin/CTF_Support.php#L554
- https://plugins.trac.wordpress.org/browser/custom-twitter-feeds/tags/2.10.0/inc/ctf-functions.php#L207
- https://plugins.trac.wordpress.org/browser/custom-twitter-feeds/tags/2.10.0/inc/CtfFeed.php#L1072
- https://plugins.trac.wordpress.org/browser/custom-twitter-feeds/tags/2.10.0/inc/CtfCache.php#L179
- https://plugins.trac.wordpress.org/browser/custom-twitter-feeds/tags/2.10.0/inc/SB_Twitter_Cron_Updater.php#L47
- https://plugins.trac.wordpress.org/browser/custom-twitter-feeds/tags/2.10.0/admin/views/support/content.php#L123
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3799152%40custom-twitter-feeds&new=3799152%40custom-twitter-feeds
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-116536
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-116536"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- smub Custom Twitter Feeds – A Tweets Widget or X Feed Widget
through 2.11.1
Evidence 10
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-116536
Is CVE-2026-116536 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-116536?
Custom Twitter Feeds – A Tweets Widget or X Feed Widget: through 2.11.1.Source: cve.now feed data