How severe is GHSA-9v8p-m85m-f7mm?

No CVSS score has been assigned to GHSA-9v8p-m85m-f7mm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9v8p-m85m-f7mm?

GHSA-9v8p-m85m-f7mm affects the following packages: mautic/core (Packagist), mautic/core (Packagist), mautic/core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-9v8p-m85m-f7mm?

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

How do I detect GHSA-9v8p-m85m-f7mm in my Packagist dependencies?

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.

How do I mitigate GHSA-9v8p-m85m-f7mm if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-9v8p-m85m-f7mm?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-9v8p-m85m-f7mm can be triaged on real exposure rather than presence alone.

Is GHSA-9v8p-m85m-f7mm actively exploited in the wild?

No public exploit code has been indexed for GHSA-9v8p-m85m-f7mm 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-9v8p-m85m-f7mm?

GHSA-9v8p-m85m-f7mm has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 24th 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-9v8p-m85m-f7mm?

GHSA-9v8p-m85m-f7mm is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-9v8p-m85m-f7mm published, and has it been updated?

GHSA-9v8p-m85m-f7mm was published on September 3, 2025 and was last updated on September 3, 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

GHSA-9v8p-m85m-f7mm — mautic/core

GHSA-9v8p-m85m-f7mm is a Cross-site Scripting (XSS) vulnerability in mautic/core. A fix is available for mautic/core — see the affected versions and patch details below.

Mautic vulnerable to reflected XSS in lead:addLeadTags - Quick Add

Also known asCVE-2025-9823

Published

Sep 3, 2025

Updated

Sep 3, 2025

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Sep 21, 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-9v8p-m85m-f7mm.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs24th percentile — riskier than 24% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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 Cross-Site Scripting (XSS) vulnerability allows an attacker to execute arbitrary JavaScript in the context of another user’s session. This occurs because user-supplied input is reflected back in the server’s response without proper sanitization or escaping, potentially enabling malicious actions such as session hijacking, credential theft, or unauthorized actions in the application.

Details

The vulnerability resides in the “Tags” input field on the /s/ajax?action=lead:addLeadTags endpoint. Although the server applies sanitization before storing the data or returning it later, the payload is executed immediately in the victim’s browser upon reflection, allowing an attacker to run arbitrary JavaScript in the user’s session.

Impact

A Reflected XSS attack can have a significant impact, allowing attackers to steal sensitive user data like cookies, redirect users to malicious websites, manipulate the web page content, and essentially take control of a user's session within an application by executing malicious JavaScript code within the victim's browser, even if the server-side code is secure; essentially enabling them to perform actions as if they were the logged-in user.

References

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`mautic/core`	≥ 4.4.0&&< 4.4.17	4.4.17`composer require mautic/core:^4.4.17`
🐘Packagist	`mautic/core`	≥ 5.0.0-alpha&&< 5.2.8	5.2.8`composer require mautic/core:^5.2.8`
🐘Packagist	`mautic/core`	≥ 6.0.0-alpha&&< 6.0.5	6.0.5`composer require mautic/core:^6.0.5`

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mautic/core to 4.4.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9v8p-m85m-f7mm is resolved across your whole dependency graph.
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-9v8p-m85m-f7mm can be triaged on real exposure rather than presence alone.

Tailored to GHSA-9v8p-m85m-f7mm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary A Cross-Site Scripting (XSS) vulnerability allows an attacker to execute arbitrary JavaScript in the context of another user’s session. This occurs because user-supplied input is reflected back in the server’s response without proper sanitization or escaping, potentially enabling malicious actions such as session hijacking, credential theft, or unauthorized actions in the application. ## Details The vulnerability resides in the “Tags” input field on the /s/ajax?action=lead:addLeadTags endpoint. Although the server applies sanitization before storing the data or returning it later

O3 Security · Impact-Aware SCA

Is GHSA-9v8p-m85m-f7mm in your dependencies?

O3 Security finds GHSA-9v8p-m85m-f7mm across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works