NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

CVE-2022-1330 — fullpage.js

CRITICALFix: alvarotrigo/fullpage.js@e7a5db4

CVE-2022-1330 is a critical-severity (CVSS 9.4) Cross-site Scripting (XSS) vulnerability in fullpage.js. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for fullpage.js — see the affected versions and patch details below.

stored xss due to unsantized anchor url in alvarotrigo/fullpage.js

Also known asGHSA-h3cq-j957-vhxg
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs57th percentile — riskier than 57% of all scored CVEsHighest risk
0.00%0.44%0.88%1.33%0.3%0.8%May 26Sep 26Nov 26

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

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.

23other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
fullpage.jsnpm
11Kdownloads / week

Description

using fullpage.js you can create a anchor tag . But when put href in anchor then it does not sanitize the url which allow for a break in the context of anchor element and can add our new element.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmfullpage.jsall versions4.0.5npm install fullpage.js@4.0.5

Affected Products

1 product · 1 configurations
Application
fullpagefullpage_project
< 4.0.4
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

stored xss due to unsantized anchor url in GitHub repository alvarotrigo…

huntr.devNVDApr 2022

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update fullpage.js to 4.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-1330 is resolved across your whole dependency graph.

  3. 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

using fullpage.js you can create a anchor tag . But when put href in anchor then it does not sanitize the url which allow for a break in the context of anchor element and can add our new element.
O3 Security · Impact-Aware SCA

Is CVE-2022-1330 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2022-1330: fullpage.js — Fixed in 4.0.5