Skip to content

Improve CVE-2026-26026 SSTI check and correct severity to 7.2#23

Open
UncleJ4ck wants to merge 1 commit into
Orange-Cyberdefense:mainfrom
UncleJ4ck:glpi-cve-2026-26026
Open

Improve CVE-2026-26026 SSTI check and correct severity to 7.2#23
UncleJ4ck wants to merge 1 commit into
Orange-Cyberdefense:mainfrom
UncleJ4ck:glpi-cve-2026-26026

Conversation

@UncleJ4ck

Copy link
Copy Markdown

Split from #12. This reworks the existing CVE-2026-26026 module rather than adding a new one, so compare it against the current version and take whichever you prefer.

  • check() now uses a Twig arithmetic probe ({{31337*2}} must render as 62674), which a static reflection cannot fake, and purges the draft form afterwards.
  • run(cmd) executes a command through the double-compilation SSTI (call(_get.fn, [_get.arg]) -> shell_exec) and returns stdout.
  • @cvss corrected 6.4 -> 7.2. The double-compilation is a proven shell_exec RCE, not just SSTI; 7.2 is the authenticated-admin score from GHSA-2c98-648q-h27h (the advisory also lists 9.1). Verified live: run(cmd=id) returned uid=33(www-data) on 11.0.2.
  • @author left as Zax (the researcher).

@UncleJ4ck UncleJ4ck force-pushed the glpi-cve-2026-26026 branch from afcde62 to 9e5e29e Compare June 17, 2026 17:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant