CVE-2025-11345
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 flaw has been found in ILIAS up to 8.23/9.13/10.1. Affected by this issue is the function unserialize of the component Test Import. This manipulation causes deserialization. It is possible to initiate the attack remotely. Upgrading to version 8.24, 9.14 and 10.2 can resolve this issue. Upgrading the affected component is advised.
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 deserialization vulnerability in the Test Import component of ILIAS. The application uses the unsafe unserialize() function on data from test imports, allowing remote attackers to inject malicious serialized PHP objects that can lead to remote code execution.
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 installed ILIAS versionLocate the version file or admin interface that displays the ILIAS version numberAffected if The installed version matches 8.23, 9.13, or 10.1 exactly
-
Verify Test Import component is presentConfirm the Test Import module is installed and accessible in the ILIAS deploymentAffected if The Test Import component exists in the environment
-
Check for unsafe unserialize in test import codeReview PHP source files related to test imports for usage of unserialize() on user-supplied data without prior sanitizationAffected if Code uses unserialize() on data from test imports without validation
-
Determine if test import functionality is enabled for usersReview ILIAS user role permissions and test import feature configuration to see if any roles can access test importAffected if Users with access to test import functionality exist in the system
An environment is affected if it runs ILIAS version 8.23, 9.13, or 10.1 and has the Test Import component enabled with the vulnerable unserialize() call present in the code.
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 patch the unsafe unserialize call in the Test Import component.
ILIAS 8.24, 9.14, or 10.2 (depending on your current major version line)
- Identify your current ILIAS version (8.x, 9.x, or 10.x) by checking the installation or administration interface
- For ILIAS 8.x: Upgrade to version 8.24
- For ILIAS 9.x: Upgrade to version 9.14
- For ILIAS 10.x: Upgrade to version 10.2
- Download the updated ILIAS release from the official ILIAS repository (https://www.ilias.de/download/)
- Back up the existing ILIAS database and file directory before proceeding
- Follow the standard ILIAS upgrade procedure for your version
- Verify the upgrade was successful and the version number reflects the patched release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11345 — 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-11345 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