Answer in brief
CVE-2026-104904 records a Medium severity (CVSS 6.5) vulnerability in Shortcodes Ultimate <= 7.9.1 - Unauthenticated Local File Inclusion via 'Host' Header via %CURRENT_URL% in [su_qrcode]. The current sources do not mark it as known exploited. The current feed maps gn_themes/Shortcodes Ultimate – Content Elements (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps gn_themes/Shortcodes Ultimate – Content Elements (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| gn_themes/Shortcodes Ultimate – Content Elementsgeneric | >=0 <=7.9.1 | Not reported |
Published upstream
Nov 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 21, 2026
The Shortcodes Ultimate plugin for WordPress is vulnerable to Local File Inclusion in versions up to, and including, 7.9.1 This is due to su_get_current_url() interpolating the raw Host request header into the authority portion of a URL that is then passed to esc_url() — which by design preserves '[' and ']' inside the authority so IPv6 literal hosts remain valid — and the [su_qrcode] shortcode substituting that value into its data attribute (the documented %CURRENT_URL% token) before feeding it to do_shortcode(). This makes it possible for unauthenticated attackers to include arbitrary PHP files that reside within the active theme's root directory (bounded because '/' inside an attribute value terminates parse_url()'s host and is then percent-encoded and stripped), and — when the shipped-default 'Unsafe features' option remains on — to read arbitrary post meta of any post, on any front-end page that renders [su_qrcode data="%CURRENT_URL%"].
Quoted source text, attributed separately from HOL analysis.