CVE-2022-24980 is a high-severity (CVSS 7.5) Server-Side Request Forgery (SSRF) vulnerability in kitodo/presentation. A fix is available for kitodo/presentation — see the affected versions and patch details below.
SSRF in Kitodo.Presentation
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2022-24980 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
kitodo/presentation🐘kitodo/presentation🐘kitodo/presentationReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | kitodo/presentation | all versions | 2.3.2composer require kitodo/presentation:^2.3.2 |
| 🐘Packagist | kitodo/presentation | ≥ 3.0.0&&< 3.2.3 | 3.2.3composer require kitodo/presentation:^3.2.3 |
| 🐘Packagist | kitodo/presentation | ≥ 3.3.0&&< 3.3.4 | 3.3.4composer require kitodo/presentation:^3.3.4 |
Affected Products
kitodo.presentationkitodoDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for kitodo/presentation, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update kitodo/presentation to 2.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24980 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.
Frequently Asked Questions
Is CVE-2022-24980 in your dependencies?
Find it across Packagist, including transitive dependencies.