PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-94103 RooCMS CVE debrief

A vulnerability was found in RooCMS up to 1.2.2/1.3.4/1.4RC2 in the function eval of the file roocms/site_pagePHP.php of the component Frontend Rendering. This leads to code injection. The attack can be launched remotely. The vulnerability impacts the function eval of the file roocms/site_pagePHP.php of the component Frontend Rendering in RooCMS up to 1.2.2/1.3.4/1.4RC2, leading to code injection. Defenders responsible for RooCMS installations, especially in remote deployment contexts, should assess exposure to this code injection vulnerability and prioritize verification and potential remediation.

Vendor
RooCMS
Product
RooCMS
CVSS
LOW 2
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-21
Original CVE updated
2026-09-21
Advisory published
2026-09-21
Advisory updated
2026-09-21

Who should care

Defenders responsible for RooCMS installations, especially in remote deployment contexts, should assess exposure to this code injection vulnerability and prioritize verification and potential remediation.

Why it matters

Defenders should prioritize verifying exposure of RooCMS installations to this code injection vulnerability, especially in remote deployment contexts, and consider compensating controls for unpatched instances.

  • Verify exposure of RooCMS installations to code injection
  • Assess remote deployment contexts for potential attack vectors
  • Consider compensating controls for unpatched RooCMS instances

Technical summary

The vulnerability impacts the function eval of the file roocms/site_pagePHP.php of the component Frontend Rendering in RooCMS up to 1.2.2/1.3.4/1.4RC2, leading to code injection. The attack can be launched remotely. Defenders responsible for RooCMS installations, especially in remote deployment contexts, should assess exposure to this code injection vulnerability and prioritize verification and potential remediation. The CVE record and NVD entry provide details on the vulnerability, including its CVSS score of 2 and severity of LOW.

Defensive priority

Defenders should prioritize verifying exposure of RooCMS installations to this code injection vulnerability, especially in remote deployment contexts.

Recommended defensive actions

  • Verify RooCMS installations for exposure to this code injection vulnerability
  • Assess remote deployment contexts for potential attack vectors
  • Consider compensating controls for unpatched RooCMS instances
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
  • 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.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its CVSS score of 2 and severity of LOW. However, the vendor did not respond to early disclosure. The vulnerability was found in RooCMS up to 1.2.2/1.3.4/1.4RC2 in the function eval of the file roocms/site_pagePHP.php of the component Frontend Rendering. This leads to code injection. The attack can be launched remotely.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-94103 CVE Program record

    Publisher, destination, and source semantics verified

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

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

  • CVE-2026-94103 NVD vulnerability detail

    Publisher, destination, and source semantics verified

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

    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.