How severe is GHSA-jfcc-rm7f-xgf8?

GHSA-jfcc-rm7f-xgf8 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-jfcc-rm7f-xgf8?

GHSA-jfcc-rm7f-xgf8 affects the following packages: mavon-editor (npm). Ecosystems affected: npm.

How do I fix GHSA-jfcc-rm7f-xgf8?

Update mavon-editor to 2.8.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jfcc-rm7f-xgf8 is resolved across your whole dependency graph.

How do I detect GHSA-jfcc-rm7f-xgf8 in my npm dependencies?

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

How do I mitigate GHSA-jfcc-rm7f-xgf8 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-jfcc-rm7f-xgf8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-jfcc-rm7f-xgf8 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.

When was GHSA-jfcc-rm7f-xgf8 published, and has it been updated?

GHSA-jfcc-rm7f-xgf8 was published on September 3, 2020 and was last updated on September 29, 2021. 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

MEDIUM severity

Cross-Site Scripting in mavon-editorGHSA-jfcc-rm7f-xgf8

MEDIUMFix: hinesboy/mavonEditor#548

GHSA-jfcc-rm7f-xgf8 is a medium-severity (CVSS 6.5) vulnerability in mavon-editor. A fix is available for mavon-editor — see the affected versions and patch details below.

Published

Sep 3, 2020

Updated

Sep 29, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 29, 2021 · OSV.dev, 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.

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

mavon-editornpm

22Kdownloads / week

Description

All versions of mavon-editor are vulnerable to Cross-Site Scripting. The package fails to sanitize entered input, allowing attackers to execute arbitrary JavaScript in a victim's browser.

Recommendation

No fix is currently available. Consider using an alternative package until a fix is made available.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`mavon-editor`	all versions	2.8.2`npm install mavon-editor@2.8.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mavon-editor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mavon-editor to 2.8.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jfcc-rm7f-xgf8 is resolved across your whole dependency graph.
Workarounds
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

All versions of `mavon-editor` are vulnerable to Cross-Site Scripting. The package fails to sanitize entered input, allowing attackers to execute arbitrary JavaScript in a victim's browser. ## Recommendation No fix is currently available. Consider using an alternative package until a fix is made available.

O3 Security · Impact-Aware SCA

Is GHSA-jfcc-rm7f-xgf8 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works