Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-80428 – Unauthenticated PHP Object Injection / RCE – ILIAS before 9.22, 10.10, 11.3

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-80428 is a critical unauthenticated PHP Object Injection vulnerability (CWE-502) affecting the ILIAS open-source learning management system. The flaw resides in the Shibboleth logout endpoint, which deserializes stored session data without restricting the classes that may be constructed, ultimately allowing remote code execution as the web server user. The issue carries a CVSS v3.1 base score of 9.8 (Critical) and requires no authentication or user interaction to exploit.

Technical details

  • Root cause: components/ILIAS/AuthShibboleth/resources/shib_logout.php is exempted from authentication by ilInitialisation. Its logout-notification handler reads every live session table row and passes each row’s stored data to a hand-written parser that calls unserialize() without restricting which classes may be constructed.
  • Trigger/precondition: An attacker can place a serialized object into a session row without logging in, because the LTI authentication entry point stores request parameters into the session and is reachable on a path exempted from authentication by the same initialisation code.
  • Attack vector: Network, no privileges required, no user interaction (CVSS AV:N/AC:L/PR:N/UI:N).
  • Impact: Any serialized object present in a session row is instantiated for an anonymous request, and its destructor executes when the object is discarded. A class bundled with the application writes a JSON-encoded structure to a file named by one of its own properties on destruction, letting an attacker place attacker-controlled content at an attacker-chosen path below the web root — resulting in code execution as the web server user.

Affected software

  • ILIAS versions before 9.22
  • ILIAS 10.0 through 10.9
  • ILIAS 11.0 through 11.2

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade to ILIAS 9.22, 10.10, or 11.3, which remove the vulnerable logout-notification implementation in the Shibboleth logout endpoint.
  • If immediate patching is not possible: Restrict or block external access to the Shibboleth (shib_logout.php) and LTI authentication endpoints at the network/web-server layer until the upgrade can be applied, and monitor for unexpected file writes below the web root.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: ILIAS ... Login, Login to ILIAS, ILIAS: Login to ILIAS, ending in - ILIAS Login Page
  • Raw response body: Powered by ILIAS (v<version> <date>), Login to ILIAS

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge