Skip to main content
VulnerabilityPublished

CVE-2026-104904: Shortcodes Ultimate (WordPress plugin) · Remote File Include

Affects Shortcodes Ultimate (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium.

Data as of 21 Nov 2026, 08:13 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.16.5
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
gn_themesShortcodes Ultimate – Content ElementsAffected
  • <=7.9.1
Fixed in–

AI-suggested

Users should disable the 'Unsafe features' option in the plugin settings to mitigate the risk of arbitrary post meta disclosure. Until an official fix is released, avoid using the [su_qrcode] shortcode with the %CURRENT_URL% token or restrict access to affected pages. Monitor the vendor's advisory channels for updates and apply patches once available.

Description

The Shortcodes Ultimate plugin for WordPress versions up to and including 7.9.1 contains a Local File Inclusion vulnerability. This flaw arises from unsafe handling of the Host request header in the su_get_current_url() function, which is then used in the [su_qrcode] shortcode. Unauthenticated attackers can exploit this to include arbitrary PHP files from the active theme's root directory and potentially read arbitrary post meta data if the 'Unsafe features' option is enabled.

References

Community reviews

Loading reviews…