dbcve.org
Kitodo.presentationTYPO3 extension · Kitodo

CVE-2022-24980

HIGH · 7.5 CVSS v3.1 Published 2022-02-19
Fix available
A fix is available. Upgrade to 2.3.2 / 3.2.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
An issue was discovered in the Kitodo.Presentation (aka dif) extension before 2.3.2, 3.x before 3.2.3, and 3.3.x before 3.3.4 for TYPO3. A missing access check in an eID script allows an unauthenticated user to submit arbitrary URLs to this component. This results in SSRF, allowing attackers to view the content of any file or webpage the webserver has access to.

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 confidence

The Kitodo.Presentation TYPO3 extension before versions 2.3.2, 3.2.3, and 3.3.4 contains a Server-Side Request Forgery (SSRF) vulnerability. An eID script lacks proper access control, allowing unauthenticated attackers to submit arbitrary URLs. This enables viewing of any file or webpage accessible to the webserver, including local file system contents.

MitigationUpgrade the Kitodo.Presentation extension to version 2.3.2, 3.2.3, 3.3.4 or later, which contains the access check fix. If immediate patching is not possible, disable or restrict access to the vulnerable eID script via TYPO3 configuration or web server rules.

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
Kitodo.presentationTYPO3 extension
Affected:< 2.3.2>= 3.0.0, < 3.2.3>= 3.3.0, < 3.3.4

CVSS 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Kitodo.Presentation extension is installed
    Check the TYPO3 extension manager or list installed extensions for 'Kitodo.presentation' or 'kitodo_presentation'
    Affected if The extension appears in the installed extensions list
  2. Identify installed version number
    In TYPO3 extension manager, view the version details of the Kitodo.Presentation extension, or check the ext_emconf.php file in the extension directory
    Affected if Version is < 2.3.2, OR >= 3.0.0 and < 3.2.3, OR >= 3.3.0 and < 3.3.4
  3. Locate the vulnerable eID script
    Search for the eID script file in the extension directory, typically named 'eId.php' or similar in the ext/kitodo_presentation/ directory
    Affected if The eID script file exists in the extension directory
  4. Verify the eID endpoint is accessible
    Attempt to access the eID endpoint via a web request to a URL pattern like /?eID=kitodo_presentation or /index.php?eID=kitodo_presentation (use a non-malicious test URL if testing)
    Affected if The endpoint responds without requiring authentication or authorization checks
  5. Confirm file reading capability
    If testing is permitted, send a request to the eID endpoint with a local file path such as file:///etc/passwd or ../ to observe if file contents are returned
    Affected if The response contains contents of local files or the server returns file data from arbitrary paths

If the Kitodo.Presentation extension is installed and its version falls within the affected ranges, and the eID script is accessible without authentication, the environment is vulnerable to SSRF.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.3.2 / 3.2.3 / 3.3.4 or later
Fixed in 2.3.23.2.33.3.4
Interim mitigation

Upgrade the Kitodo.Presentation extension to version 2.3.2, 3.2.3, 3.3.4 or later, which contains the access check fix. If immediate patching is not possible, disable or restrict access to the vulnerable eID script via TYPO3 configuration or web server rules.

Recommended fix High confidence

Upgrade to 2.3.2+ (for 2.x) or 3.2.3+ (for 3.0-3.2.x) or 3.3.4+ (for 3.3.x)

  1. 1. Identify the current installed version of Kitodo.presentation extension in your TYPO3 instance
  2. 2. If using TYPO3 2.x (version < 2.3.2): Plan upgrade to version 2.3.2 or later
  3. 3. If using TYPO3 3.0.0 - 3.2.x: Plan upgrade to version 3.2.3 or later
  4. 4. If using TYPO3 3.3.0 - 3.3.x: Plan upgrade to version 3.3.4 or later
  5. 5. Create a complete backup of the TYPO3 database and files before updating
  6. 6. Update the Kitodo.presentation extension via TYPO3 Extension Manager or Composer (composer update kitodo/presentation)
  7. 7. Clear all TYPO3 caches after the update
  8. 8. Verify the new version is installed correctly
Caveat Review release notes for any breaking changes between your current version and target version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Kitodo.presentation Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-24980 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-24980 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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