CVE-2025-11346
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability has been found in ILIAS up to 8.23/9.13/10.1. This affects the function unserialize of the component Base64 Decoding Handler. Such manipulation of the argument f_settings leads to deserialization. It is possible to launch the attack remotely. Upgrading to version 8.24, 9.14 and 10.2 is able to mitigate this issue. It is advisable to upgrade the affected component.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a PHP Object Injection vulnerability in ILIAS where the Base64 Decoding Handler uses unserialize() on the user-controlled f_settings parameter. By crafting malicious Base64-encoded serialized PHP objects, a remote attacker can trigger deserialization leading to remote code execution or other attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 8.23= 9.13= 10.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify ILIAS versionCheck the installed ILIAS version. This is typically found in the ilias.ini.php file, a version file, or by accessing the ILIAS administration panel. On the filesystem, look for a version.php or similar version indicator file in the ILIAS root directory.Affected if The installed version is 8.23, 9.13, or 10.1 exactly (these are the affected versions).
-
Locate Base64 Decoding HandlerSearch the ILIAS source code for the Base64 Decoding Handler class or file. Look for PHP files that handle Base64 encoding/decoding operations, particularly those that process user input.Affected if The Base64 Decoding Handler file exists in the ILIAS installation and is accessible via web requests.
-
Inspect f_settings parameter handlingExamine the Base64 Decoding Handler code for the f_settings parameter. Look for code that takes the f_settings GET or POST parameter and passes it through Base64 decoding followed by unserialize().Affected if The code contains an unserialize() call operating on the decoded f_settings parameter without prior validation.
-
Verify parameter is user-controlledConfirm that the f_settings parameter originates from user HTTP requests (GET/POST) and flows directly to the unserialize() call without sanitization.Affected if The f_settings parameter comes directly from user input and reaches the unserialize() function without filtering.
You are affected if your ILIAS installation is version 8.23, 9.13, or 10.1 AND the Base64 Decoding Handler processes user-supplied f_settings parameters through unserialize().
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade ILIAS to version 8.24, 9.14, or 10.2 to replace the insecure unserialize() call with safe deserialization methods.
8.24 (if currently on 8.23) | 9.14 (if currently on 9.13) | 10.2 (if currently on 10.1)
- Determine your current ILIAS version (8.23, 9.13, or 10.1) by checking the login page or administration area
- Back up your entire ILIAS installation directory and database before proceeding
- Download the corresponding fixed version: 8.24 for ILIAS 8.x, 9.14 for ILIAS 9.x, or 10.2 for ILIAS 10.x from the official ILIAS repository
- Extract the new version files to a temporary location
- Replace the existing ILIAS files with the new version files, preserving custom configurations in ./Customizing/ and ./data/ directories
- Run the ILIAS update wizard by accessing the ILIAS URL as administrator
- Follow the on-screen prompts to complete database updates and schema migrations
- Verify the installation by logging in and checking the ILIAS version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11346 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-11346 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data