PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-89145 flextype CVE debrief

Flextype CMS versions 0.9.9 through 1.0.0-alpha.3 have a vulnerability where plugin directory names are not HTML-escaped in the dependency error page. This allows attackers with write access to the plugins directory to create a plugin with HTML characters in its name, potentially leading to script execution in users' browsers when dependency validation fails.

Vendor
flextype
Product
Unknown
CVSS
LOW 2.4
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-11
Original CVE updated
2026-09-11
Advisory published
2026-09-11
Advisory updated
2026-09-11

Who should care

Defenders responsible for Flextype CMS installations, particularly those with write access to the plugins directory, should assess exposure and verify proper HTML escaping of plugin directory names to prevent potential script execution.

Why it matters

Defenders should care about CVE-2026-89145 because it allows attackers with write access to plugin directories to potentially execute scripts in users' browsers. This requires verification of plugin directory names and proper HTML escaping to prevent script execution. Affected roles include developers and administrators of Flextype CMS installations. The vulnerability has a CVSS score of 2.4 and is considered low severity.

  • Potential script execution in users' browsers when dependency validation fails
  • Possible data theft or unauthorized actions through XSS
  • Required verification of plugin directory names for proper HTML escaping
  • Necessity to restrict write access to plugins directory

Technical summary

Flextype CMS versions 0.9.9 through 1.0.0-alpha.3 do not HTML-escape plugin directory names in the dependency error page rendered by getValidPluginsDependencies(). This allows attackers with write access to the plugins directory to create a plugin with HTML characters in its name, potentially leading to script execution in users' browsers when dependency validation fails. The vulnerability has a CVSS score of 2.4 and is considered low severity. Defenders should prioritize verifying plugin directory names and ensuring proper HTML escaping to prevent potential script execution.

Defensive priority

Defenders should prioritize verifying plugin directory names and ensuring proper HTML escaping to prevent potential script execution.

Recommended defensive actions

  • Verify plugin directory names for proper HTML escaping
  • Ensure write access to plugins directory is restricted
  • Monitor for suspicious plugin directory name changes
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description and affected versions. Flextype CMS versions 0.9.9 through 1.0.0-alpha.3 are confirmed affected. Defenders should verify plugin directory names and ensure proper HTML escaping to prevent potential script execution. Evidence is limited to public CVE and NVD records.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-89145 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-89145

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-89145 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-89145

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.