CVE-2018-11647 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in oauth2orize-fprm. A fix is available for oauth2orize-fprm — see the affected versions and patch details below.
oauth2orize-fprm XSS vulnerability
EPSS Exploitation Probability
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
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.
oauth2orize-fprmnpmDescription
index.js in oauth2orize-fprm before 0.2.1 has XSS via a crafted URL.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | oauth2orize-fprm | all versions | 0.2.1npm install oauth2orize-fprm@0.2.1 |
Affected Products
oauth2orize-fprmoauth2orize-fprm_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for oauth2orize-fprm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update oauth2orize-fprm to 0.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-11647 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
Is CVE-2018-11647 in your dependencies?
Find it across npm, including transitive dependencies.