Skip to content

← Public intelligence

npm package

fullpage.js

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.4npmAmendedPublished

    Cross-site Scripting in fullpage.js

    CVE-2022-1330 · GHSA-h3cq-j957-vhxg

    Affected
    • npm fullpage.js < 4.0.5
    Fixed in
    4.0.5· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 4.0.5 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  2. High, CVSS 7.3npmAmendedPublished

    Prototype Pollution in fullpage.js

    CVE-2022-1295 · GHSA-vpgw-ffh3-648h

    Affected
    • npm fullpage.js < 4.0.2
    Fixed in
    4.0.2· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 4.0.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →