NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

CVE-2025-9822 — core

MEDIUMFix: mautic/mautic@882c2c5

CVE-2025-9822 is a medium-severity (CVSS 5.5) CWE-283 vulnerability in mautic/core. A fix is available for mautic/core — see the affected versions and patch details below.

Secret data extraction via elfinder

Also known asGHSA-438m-6mhw-hq5w
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-9822.

EPSS Exploitation Probability

via FIRST.org ↗
0.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs15th percentile — riskier than 15% of all scored CVEsHighest risk
0.00%0.25%0.49%0.74%0.0%0.2%May 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected
🐘mautic/core🐘mautic/core🐘mautic/core

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

Summary

A user with administrator rights can change the configuration of the mautic application and extract secrets that are not normally available.

Impact

An administrator who usually does not have access to certain parameters, such as database credentials, can disclose them.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistmautic/core≥ 4.4.0&&< 4.4.174.4.17composer require mautic/core:^4.4.17
🐘Packagistmautic/core≥ 5.0.0-alpha&&< 5.2.85.2.8composer require mautic/core:^5.2.8
🐘Packagistmautic/core≥ 6.0.0-alpha&&< 6.0.56.0.5composer require mautic/core:^6.0.5

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update mautic/core to 4.4.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-9822 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Summary _A user with administrator rights can change the configuration of the mautic application and extract secrets that are not normally available._ ### Impact _An administrator who usually does not have access to certain parameters, such as database credentials, can disclose them._
O3 Security · Impact-Aware SCA

Is CVE-2025-9822 in your dependencies?

Find it across Packagist, including transitive dependencies.

CVE-2025-9822: core — Fixed in 4.4.17