CVE-2021-23648 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in @braintree/sanitize-url. 1 public exploit reference exists, so weaponization risk is real. A fix is available for @braintree/sanitize-url — see the affected versions and patch details below.
Cross-site Scripting in sanitize-url
EPSS Exploitation Probability
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.
How urgent is this, really
CVE-2021-23648 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
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.
@braintree/sanitize-urlnpmDescription
The package @braintree/sanitize-url before 6.0.0 is vulnerable to Cross-site Scripting (XSS) due to improper sanitization in the sanitizeUrl function.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @braintree/sanitize-url | all versions | 6.0.0npm install @braintree/sanitize-url@6.0.0 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @braintree/sanitize-url, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @braintree/sanitize-url to 6.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-23648 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 CVE-2021-23648 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2021-23648. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 8 | grafana-0:7.5.15-3.el8 | RHSA-2022:7519 |
| Red Hat Enterprise Linux 9 | grafana-0:7.5.15-3.el9 | RHSA-2022:8057 |
| Red Hat OpenShift Container Platform 4.11 | openshift4/ose-grafana:v4.11.0-202208020235.p0.g6773185.assembly.stream | RHSA-2022:5069 |
Frequently Asked Questions
Is CVE-2021-23648 in your dependencies?
O3 Security finds CVE-2021-23648 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.