CVE-2025-9822 json
Secret data extraction via elfinder
published last yr. modified 21d ago also GHSA-438m-6mhw-hq5w , EUVD-2025-26505
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
SummaryA user with administrator rights can change the configuration of the mautic application and extract secrets that are not normally available.
ImpactAn administrator who usually does not have access to certain parameters, such as database credentials, can disclose them.
Patch / fix
- packagist mautic/core 4.4.17, 5.2.8, 6.0.5
- Mautic Mautic < 4.4.17, < 5.2.8, < 6.0.5
Is CVE-2025-9822 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 FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N |
| GitHub | 3.1 | 5.5 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | mautic/core | >=4.4.0, <4.4.17 >=5.0.0-alpha, <5.2.8 >=6.0.0-alpha, <6.0.5 |
4.4.17 5.2.8 6.0.5 |
Affected products
- Mautic Mautic
Classification
- Weakness
-
- CWE-283 Unverified Ownership
References
-
github.com
/mautic/mautic/commit/882c2c5be646e36f7b91e7c4b24f71aafa617cd5
web
-
github.com
/mautic/mautic/commit/a310b1933de7cfefec03382a4d8c0d9dbbaa0600
web
-
github.com
/mautic/mautic/security/advisories/GHSA-438m-6mhw-hq5w
web
-
nvd.nist.gov
/vuln/detail/CVE-2025-9822
advisory
-
github.com
/mautic/mautic
package
Sources
- CVE List CVE-2025-9822
- GitHub Advisory GHSA-438m-6mhw-hq5w
- NVD CVE-2025-9822
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.