FKIE_CVE-2026-97640

Vulnerability from fkie_nvd - Published: 2026-10-16 07:17 - Updated: 2026-10-16 15:17
Severity
7.2 (High) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Summary
The WPConsent – Cookie Banner & Cookie Consent for Privacy Compliance (GDPR / CCPA / EU Compliance Cookie Notice) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content via Simple HTML DOM Parser Noise-Key Restoration (mXSS) in all versions up to, and including, 1.1.9 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires the Script Blocking feature to be enabled, and the exploit chain depends on an attacker submitting two coordinated comments — one embedding event-handler syntax inside an allowed <code> element and one placing the deterministic ___noise___ restoration key inside an allowed <abbr title=""> attribute — with the key offset confirmable via an unauthenticated wpconsent_debug=1 request.
References
security@wordfence.comhttps://plugins.trac.wordpress.org/browser/wpconsent-cookies-banner-privacy-suite/tags/1.1.9/includes/class-wpconsent-cookie-blocking.php#L107
security@wordfence.comhttps://plugins.trac.wordpress.org/browser/wpconsent-cookies-banner-privacy-suite/tags/1.1.9/includes/class-wpconsent-cookie-blocking.php#L222
security@wordfence.comhttps://plugins.trac.wordpress.org/browser/wpconsent-cookies-banner-privacy-suite/tags/1.1.9/lib/simplehtmldom/class-wpconsent-simple-html-dom.php#L2135
security@wordfence.comhttps://plugins.trac.wordpress.org/browser/wpconsent-cookies-banner-privacy-suite/tags/1.1.9/lib/simplehtmldom/class-wpconsent-simple-html-dom.php#L2236
security@wordfence.comhttps://plugins.trac.wordpress.org/browser/wpconsent-cookies-banner-privacy-suite/tags/1.1.9/lib/simplehtmldom/class-wpconsent-simple-html-dom.php#L466
security@wordfence.comhttps://plugins.trac.wordpress.org/changeset/3734401/wpconsent-cookies-banner-privacy-suite/trunk/lib/simplehtmldom/class-wpconsent-simple-html-dom.php
security@wordfence.comhttps://plugins.trac.wordpress.org/changeset?reponame=&new=3734409%40wpconsent-cookies-banner-privacy-suite&old=3676065%40wpconsent-cookies-banner-privacy-suite
security@wordfence.comhttps://www.wordfence.com/threat-intel/vulnerabilities/id/e92b4189-bd07-4d29-8fe1-e9de60107e70?source=cve
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "WPConsent \u2013 Cookie Banner \u0026 Cookie Consent for Privacy Compliance (GDPR / CCPA / EU Compliance Cookie Notice)",
          "vendor": "smub",
          "versions": [
            {
              "lessThanOrEqual": "1.1.9",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "source": "security@wordfence.com"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "The WPConsent \u2013 Cookie Banner \u0026 Cookie Consent for Privacy Compliance (GDPR / CCPA / EU Compliance Cookie Notice) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content via Simple HTML DOM Parser Noise-Key Restoration (mXSS) in all versions up to, and including, 1.1.9 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires the Script Blocking feature to be enabled, and the exploit chain depends on an attacker submitting two coordinated comments \u2014 one embedding event-handler syntax inside an allowed \u0026lt;code\u0026gt; element and one placing the deterministic ___noise___ restoration key inside an allowed \u0026lt;abbr title=\"\"\u0026gt; attribute \u2014 with the key offset confirmable via an unauthenticated wpconsent_debug=1 request."
    }
  ],
  "id": "CVE-2026-97640",
  "lastModified": "2026-10-16T15:17:38.253",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 7.2,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "LOW",
          "integrityImpact": "LOW",
          "privilegesRequired": "NONE",
          "scope": "CHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 2.7,
        "source": "security@wordfence.com",
        "type": "Secondary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2026-97640",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2026-10-16T14:33:50.450736Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2026-10-16T07:17:14.823",
  "references": [
    {
      "source": "security@wordfence.com",
      "url": "https://plugins.trac.wordpress.org/browser/wpconsent-cookies-banner-privacy-suite/tags/1.1.9/includes/class-wpconsent-cookie-blocking.php#L107"
    },
    {
      "source": "security@wordfence.com",
      "url": "https://plugins.trac.wordpress.org/browser/wpconsent-cookies-banner-privacy-suite/tags/1.1.9/includes/class-wpconsent-cookie-blocking.php#L222"
    },
    {
      "source": "security@wordfence.com",
      "url": "https://plugins.trac.wordpress.org/browser/wpconsent-cookies-banner-privacy-suite/tags/1.1.9/lib/simplehtmldom/class-wpconsent-simple-html-dom.php#L2135"
    },
    {
      "source": "security@wordfence.com",
      "url": "https://plugins.trac.wordpress.org/browser/wpconsent-cookies-banner-privacy-suite/tags/1.1.9/lib/simplehtmldom/class-wpconsent-simple-html-dom.php#L2236"
    },
    {
      "source": "security@wordfence.com",
      "url": "https://plugins.trac.wordpress.org/browser/wpconsent-cookies-banner-privacy-suite/tags/1.1.9/lib/simplehtmldom/class-wpconsent-simple-html-dom.php#L466"
    },
    {
      "source": "security@wordfence.com",
      "url": "https://plugins.trac.wordpress.org/changeset/3734401/wpconsent-cookies-banner-privacy-suite/trunk/lib/simplehtmldom/class-wpconsent-simple-html-dom.php"
    },
    {
      "source": "security@wordfence.com",
      "url": "https://plugins.trac.wordpress.org/changeset?reponame=\u0026new=3734409%40wpconsent-cookies-banner-privacy-suite\u0026old=3676065%40wpconsent-cookies-banner-privacy-suite"
    },
    {
      "source": "security@wordfence.com",
      "url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/e92b4189-bd07-4d29-8fe1-e9de60107e70?source=cve"
    }
  ],
  "sourceIdentifier": "security@wordfence.com",
  "vulnStatus": "Deferred",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-79"
        }
      ],
      "source": "security@wordfence.com",
      "type": "Secondary"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.