Skip to content
Fencer Intel
medium 6.3

CVE-2025-22145 json

Carbon has an arbitrary file include via unvalidated input passed to Carbon::setLocale

published last yr. modified 4mo ago also GHSA-j3f9-p6hm-5w6q , EUVD-2025-0030

cvss
6.3
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 55%
public exploits
0
none known

Summary

Carbon is an international PHP extension for DateTime. Application passing unsanitized user input to Carbon::setLocale are at risk of arbitrary file include, if the application allows users to upload files with .php extension in an folder that allows include or require to read it, then they are at risk of arbitrary code ran on their servers. This vulnerability is fixed in 3.8.4 and 2.72.6.

Patch / fix

  • packagist nesbot/carbon 2.72.6, 3.8.4
  • php-nesbot-carbon Debian 12 2.65.0-1+deb12u1
  • php-nesbot-carbon Debian 14, Debian 13 2.72.6-1

debian advisories DEBIAN-CVE-2025-22145

Is CVE-2025-22145 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.75% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 4.0 6.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
CNA 4.0 6.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected packages

ecosystem package affected fixed in
packagist nesbot/carbon
>=3.0.0, <3.8.4
<2.72.6
3.8.4
2.72.6

Affected products

  • CarbonPHP carbon

Classification

Weakness
  • CWE-98 Improper Control of Filename for Include/Require Statement in PHP Program

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.