# CVE-2022-1295: Prototype Pollution in alvarotrigo/fullpage.js

> Prototype pollution in fullpage.js allows attackers to manipulate object prototypes, potentially leading to code execution or security bypasses.

- **Severity:** High 7.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Apr 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-vpgw-ffh3-648h

## What is CVE-2022-1295?

CVE-2022-1295 is a high-severity vulnerability in alvarotrigo/fullpage.js, published on 11 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Prototype Pollution in GitHub repository alvarotrigo/fullpage.js prior to 4.0.2.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2022-1295?

2 open source packages ship an affected version, including fullpage.js. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `fullpage.js` | npm | All versions | 4.0.2 |
| `fullpage.js` | npm | All versions | 4.0.2 |

Products: Fullpage Project Fullpage.

## How do I fix CVE-2022-1295?

Upgrade fullpage.js to 4.0.2 or later.

## Is CVE-2022-1295 being exploited?

There is no known exploitation of CVE-2022-1295 in the wild and no public exploit code.

## Other vulnerabilities in alvarotrigo/fullpage.js

- [CVE-2022-1330](https://insights.sbomify.com/CVE-2022-1330/): stored xss due to unsantized anchor url in alvarotrigo/fullpage.js (critical 9.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-1295 and fix it if it is affected.

What it is: CVE-2022-1295 is a high-severity vulnerability in alvarotrigo/fullpage.js, published on 11 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-1295 in the wild and no public exploit code.

Affected packages and fixed versions:
- fullpage.js (npm): affected all versions; fixed in 4.0.2
- fullpage.js (npm): affected all versions; fixed in 4.0.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-1295/ (Markdown: https://insights.sbomify.com/CVE-2022-1295/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-1295
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-1295
- OSV: https://osv.dev/vulnerability/CVE-2022-1295

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-1295/
Summaries are generated and may contain mistakes; the official description above is the record.