Skip to main content
CVE-2026-89095VulnerabilityPublished

The Shortcodes and extra features for Phlox theme plugin for WordPress is vulnerable to Local File Inclusion in all

Source GCVE Database

0
Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-89095· High 8.1

Not known to be exploited · CVSS 8.1 High.

Data as of 20 Nov 2026, 10:33 UTC

CVSS 3.1 base score
8.1High
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.18.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 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 19 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
avertaShortcodes and extra features for Phlox themeAffected
  • <=2.17.22
Fixed in–

AI-suggested

Until a fix is available, restrict access to the vulnerable plugin and consider disabling it if possible. Monitor vendor communications for updates and apply patches promptly once released.

Description

The Shortcodes and extra features for Phlox theme plugin for WordPress contains a Local File Inclusion (LFI) vulnerability in all versions up to and including 2.17.22 via the 'extra_template_path' parameter. This vulnerability allows unauthenticated attackers to include and execute arbitrary PHP files on the server, potentially leading to code execution, access control bypass, and exposure of sensitive data. The existing fix for a related vulnerability (CVE-2023-37888) does not fully mitigate this issue because it only restricts the filename suffix and does not validate directory traversal sequences in the 'extra_template_path' parameter.

References

Community reviews

Loading reviews…