How severe is GHSA-x3jx-5w6m-q2fc?

GHSA-x3jx-5w6m-q2fc has a CVSS score of 7/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-x3jx-5w6m-q2fc?

GHSA-x3jx-5w6m-q2fc affects the following packages: mautic/core-lib (Packagist), mautic/core-lib (Packagist), mautic/core (Packagist), mautic/core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-x3jx-5w6m-q2fc?

Update mautic/core-lib to 4.4.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x3jx-5w6m-q2fc is resolved across your whole dependency graph.

How do I detect GHSA-x3jx-5w6m-q2fc in my Packagist dependencies?

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

How do I mitigate GHSA-x3jx-5w6m-q2fc if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-x3jx-5w6m-q2fc actively exploited in the wild?

No public exploit code has been indexed for GHSA-x3jx-5w6m-q2fc yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-x3jx-5w6m-q2fc?

GHSA-x3jx-5w6m-q2fc has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 22th 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.

What type of vulnerability is GHSA-x3jx-5w6m-q2fc?

GHSA-x3jx-5w6m-q2fc is classified as Improper Authentication (CWE-287), CWE-862 (CWE-862). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-x3jx-5w6m-q2fc published, and has it been updated?

GHSA-x3jx-5w6m-q2fc was published on September 18, 2024 and was last updated on February 28, 2025. 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

HIGH severity

Mautic vulnerable to Improper Access Control in UI upgrade processGHSA-x3jx-5w6m-q2fc

HIGHFix: mautic/mautic@89f964d

GHSA-x3jx-5w6m-q2fc is a high-severity (CVSS 7) Improper Authentication vulnerability in mautic/core-lib. A fix is available for mautic/core-lib — see the affected versions and patch details below.

Also known asCVE-2022-25768

Published

Sep 18, 2024

Updated

Feb 28, 2025

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 10, 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 GHSA-x3jx-5w6m-q2fc.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs22th percentile — riskier than 22% of all scored CVEsHighest risk

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

4 pkgs affected

🐘mautic/core-lib🐘mautic/core-lib🐘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

Impact

The logic in place to facilitate the update process via the user interface lacks access control to verify if permission exists to perform the tasks. Prior to this patch being applied it might be possible for an attacker to access the Mautic version number or to execute parts of the upgrade process without permission. As upgrading in the user interface is deprecated, this functionality is no longer required.

Patches

Upgrade to 4.4.13 or 5.1.1 or later.

Workarounds

None.

For more information

If you have any questions or comments about this advisory:

Email us at [email protected]

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`mautic/core-lib`	≥ 1.1.3&&< 4.4.13	4.4.13`composer require mautic/core-lib:^4.4.13`
🐘Packagist	`mautic/core-lib`	≥ 5.0.0-alpha&&< 5.1.1	5.1.1`composer require mautic/core-lib:^5.1.1`
🐘Packagist	`mautic/core`	≥ 1.1.3&&< 4.4.13	4.4.13`composer require mautic/core:^4.4.13`
🐘Packagist	`mautic/core`	≥ 5.0.0-alpha&&< 5.1.1	5.1.1`composer require mautic/core:^5.1.1`

Affected Products

1 product · 2 configurations

Application

mauticacquia

≥ 5.0.0 && < 5.1.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mautic/core-lib, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mautic/core-lib to 4.4.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x3jx-5w6m-q2fc is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact The logic in place to facilitate the update process via the user interface lacks access control to verify if permission exists to perform the tasks. Prior to this patch being applied it might be possible for an attacker to access the Mautic version number or to execute parts of the upgrade process without permission. As upgrading in the user interface is deprecated, this functionality is no longer required. ### Patches Upgrade to 4.4.13 or 5.1.1 or later. ### Workarounds None. ### For more information If you have any questions or comments about this advisory: * Email us at [secur