Prototype Pollution in fullpage.js

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.3 · CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

EPSS

• CVE-2022-1295: 1.29% estimated exploitation activity in the next 30 days; percentile 70.27 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

fullPage utils are available to developers using window.fputils. They can use these utils for their own use-case (other than fullPage) as well. However, one of the utils deepExtend is vulnerable to Prototype Pollution vulnerability. Javascript is "prototype" language which means when a new "object" is created, it carries the predefined properties and methods of an "object" with itself like toString, constructor etc. By using prototype-pollution vulnerability, an attacker can overwrite/create the property of that "object" type. If the victim developer has used that property anywhere in the code, then it will have severe effect on the application.

Published by the source

12 Apr 2022, 00:00 UTC

Last modified by the source

8 Nov 2023, 04:07 UTC

Source last checked

26 Oct 2026, 12:16 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-vpgw-ffh3-648h

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-vpgw-ffh3-648h

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-1295

Advisory: Prototype Pollution in fullpage.js
IDs: CVE-2022-1295, GHSA-vpgw-ffh3-648h
Record: https://patchnext.com/advisories/cve-2022-1295 (revision 2, source checked 26 Oct 2026, 12:16 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: fullpage.js 4.0.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm fullpage.js: affected < 4.0.2; fixed in 4.0.2

## Suggested inspection (read-only)
- `npm ls fullpage.js --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on fullpage.js.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-vpgw-ffh3-648h (OSV record GHSA-vpgw-ffh3-648h lists affected ranges: npm fullpage.js >=0 <4.0.2 (fixed))
- Verified: https://github.com/advisories/GHSA-vpgw-ffh3-648h (GitHub-reviewed advisory GHSA-vpgw-ffh3-648h lists affected ranges: npm fullpage.js >=0 <4.0.2)

Commands are suggestions: review each one before running it.