How severe is CVE-2013-6919?

No CVSS score has been assigned to CVE-2013-6919 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2013-6919?

CVE-2013-6919 affects the following packages: james-heinrich/phpthumb (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2013-6919?

Update james-heinrich/phpthumb to 1.7.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-6919 is resolved across your whole dependency graph.

How do I detect CVE-2013-6919 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for james-heinrich/phpthumb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2013-6919 if there is no patch (or I can't update yet)?

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.

Is CVE-2013-6919 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2013-6919, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2013-6919?

CVE-2013-6919 has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 68th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2013-6919 published, and has it been updated?

CVE-2013-6919 was published on May 17, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2013-6919 — phpthumb

Fix: JamesHeinrich/phpThumb@457a37d

CVE-2013-6919 is a security vulnerability in james-heinrich/phpthumb. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for james-heinrich/phpthumb — see the affected versions and patch details below.

phpThumb is vulnerable to Server-Side Request Forgery (SSRF)

Published

May 17, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs68th percentile — riskier than 68% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐘james-heinrich/phpthumb

Real-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

The default configuration of phpThumb before 1.7.12 has a false value for the disable_debug option, which allows remote attackers to conduct Server-Side Request Forgery (SSRF) attacks via the src parameter.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`james-heinrich/phpthumb`	all versions	1.7.12`composer require james-heinrich/phpthumb:^1.7.12`

Affected Products

1 product · 1 configurations

Application

phpthumbphpthumb_project

≤ 1.7.11

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The default configuration of phpThumb before 1.7.12 has a false value fo…

rafayhackingarticles.netNVDDec 2014

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for james-heinrich/phpthumb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update james-heinrich/phpthumb to 1.7.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-6919 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

O3 Security · Impact-Aware SCA

Is CVE-2013-6919 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works