dbcve.org
Newspack PopupsWordPress extension · Automattic

CVE-2024-37476

MEDIUM · 5.4 CVSS v3.1 Published 2024-07-04
Fix available
A fix is available. Upgrade to 2.31.2 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross Site Scripting (XSS) vulnerability in Automattic Newspack Campaigns allows Stored XSS.This issue affects Newspack Campaigns: from n/a through 2.31.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Stored Cross-Site Scripting (XSS) vulnerability in Automattic Newspack Campaigns plugin allows attackers to inject malicious scripts that execute in browsers of users who view affected content. The vulnerability exists in the campaigns functionality where user-supplied input is not properly sanitized before storage and display.

MitigationUpdate Newspack Campaigns to the latest version (2.31.2 or higher) which includes proper input sanitization and output escaping. Until patched, restrict campaign management permissions to trusted users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Newspack PopupsWordPress extension
Affected:< 2.31.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Newspack Popups plugin is installed
    Access the WordPress admin dashboard, navigate to Plugins > Installed Plugins, and locate 'Newspack Popups' or 'Newspack Campaigns' in the list. Note whether it appears as an active plugin.
    Affected if The plugin appears in the installed plugins list and is activated.
  2. Check installed version against affected range
    In the Plugins page, click on the plugin to view its details, or check the version number displayed next to 'Newspack Popups'. Compare this version to 2.31.2.
    Affected if The installed version is less than 2.31.2 (for example, 2.31.1, 2.30.0, etc.).
  3. Verify campaigns functionality is in use
    Navigate to the Newspack or Campaigns section in the WordPress admin sidebar. Look for any active campaigns, popups, or reader engagement campaigns that have been created and published.
    Affected if One or more campaigns or popups exist and are published or scheduled.
  4. Inspect campaign content for unsanitized input
    Open each active campaign/popup in edit mode. Review the campaign text fields (headlines, body content, URLs, button text) for any unexpected characters, script tags, or HTML that was not intentionally added by an administrator.
    Affected if Campaign content contains raw script tags, event handlers (onclick, onerror, etc.), or other potentially malicious markup that was not intentionally configured.

A user is affected if the Newspack Popups plugin version is below 2.31.2 and there are active campaigns that could contain malicious injected scripts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.31.2 or later
Fixed in 2.31.2
Interim mitigation

Update Newspack Campaigns to the latest version (2.31.2 or higher) which includes proper input sanitization and output escaping. Until patched, restrict campaign management permissions to trusted users only.

Recommended fix High confidence

Newspack Popups 2.31.2

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Newspack Popups' (also known as 'Newspack Campaigns') plugin
  4. Check if the current version is less than 2.31.2
  5. If vulnerable, click 'Update Now' to upgrade to version 2.31.2 or later
  6. Alternatively, download the fixed version from the WordPress Plugin Repository and upload via Plugins > Add New > Upload Plugin
  7. After update, verify the new version is 2.31.2 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Newspack Popups Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-37476 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-37476 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data