How severe is GHSA-3mf5-r4hg-hfx9?

No CVSS score has been assigned to GHSA-3mf5-r4hg-hfx9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3mf5-r4hg-hfx9?

GHSA-3mf5-r4hg-hfx9 affects the following packages: mavo (npm). Ecosystems affected: npm.

How do I fix GHSA-3mf5-r4hg-hfx9?

The records we use list no patched version of mavo for GHSA-3mf5-r4hg-hfx9. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-3mf5-r4hg-hfx9 in my npm dependencies?

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

How do I mitigate GHSA-3mf5-r4hg-hfx9 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-3mf5-r4hg-hfx9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-3mf5-r4hg-hfx9 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-3mf5-r4hg-hfx9?

GHSA-3mf5-r4hg-hfx9 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 50th 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-3mf5-r4hg-hfx9?

GHSA-3mf5-r4hg-hfx9 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-3mf5-r4hg-hfx9 published, and has it been updated?

GHSA-3mf5-r4hg-hfx9 was published on March 3, 2025 and was last updated on March 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.

📦 npm

Not in CISA KEV

mavo DOM Clobbering vulnerabilityGHSA-3mf5-r4hg-hfx9

GHSA-3mf5-r4hg-hfx9 is a Cross-site Scripting (XSS) vulnerability in mavo. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asCVE-2024-53388

Published

Mar 3, 2025

Updated

Mar 3, 2025

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for GHSA-3mf5-r4hg-hfx9.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs50th percentile — riskier than 50% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

mavonpm

53downloads / week

Description

A DOM Clobbering vulnerability in mavo v0.3.2 allows attackers to execute arbitrary code via supplying a crafted HTML element.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`mavo`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

mavomavo

1 version

0.3.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mavo, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of mavo for GHSA-3mf5-r4hg-hfx9. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

A DOM Clobbering vulnerability in mavo v0.3.2 allows attackers to execute arbitrary code via supplying a crafted HTML element.

O3 Security · Impact-Aware SCA

Is GHSA-3mf5-r4hg-hfx9 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works