dbcve.org
Email Subscription PopupWordPress extension · I13websolution

CVE-2024-27960

MEDIUM · 6.1 CVSS v3.1 Published 2024-03-17
Fix available
A fix is available. Upgrade to 1.2.21 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in I Thirteen Web Solution Email Subscription Popup allows Stored XSS.This issue affects Email Subscription Popup: from n/a through 1.2.20.

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 XSS vulnerability in the Email Subscription Popup WordPress plugin allows attackers to inject malicious JavaScript through the subscription form fields. The injected payload is stored in the database and executes when administrators or users view pages displaying the subscription data.

MitigationUpdate to the latest version of the plugin if available, or implement proper input validation and output encoding on all form fields and display areas. Consider using wp_kses() and esc_html() / esc_attr() functions in WordPress.

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
Email Subscription PopupWordPress extension
Affected:< 1.2.21

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify plugin installation and version
    Locate the I13websolution Email Subscription Popup plugin in your WordPress installation (wp-content/plugins/ directory) and read the main plugin file header or check the Plugins admin page to find the installed version number.
    Affected if The installed version is lower than 1.2.21 (e.g., 1.2.20, 1.2.19, etc.)
  2. Confirm subscription form is active
    Access your WordPress admin panel and navigate to the Email Subscription Popup plugin settings to verify whether the subscription form is published and accepting submissions on any page or widget area.
    Affected if The subscription form is enabled and accessible to visitors on your site.
  3. Inspect database for suspicious stored scripts
    Query your WordPress database (typically the wp_posts or a custom subscription table created by the plugin) for any stored script tags, iframe elements, or JavaScript event handlers in subscription form submission fields such as name, email, or custom input fields.
    Affected if Database records contain unsanitized HTML tags (script, iframe, img onerror, etc.) in subscription data fields.
  4. Review admin subscription list pages
    Visit the WordPress admin pages that display subscription form submissions (usually under the plugin menu in the admin dashboard) using a browser and examine whether unsanitized user-submitted content renders as executable code when viewing the data.
    Affected if Visiting the subscription management page triggers JavaScript execution or renders HTML from stored subscription entries.

You are affected if the plugin version is below 1.2.21 AND the subscription form is active, with malicious scripts stored in the database or executing when viewing subscription data in the admin panel.

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 1.2.21 or later
Fixed in 1.2.21
Interim mitigation

Update to the latest version of the plugin if available, or implement proper input validation and output encoding on all form fields and display areas. Consider using wp_kses() and esc_html() / esc_attr() functions in WordPress.

Recommended fix High confidence

1.2.21

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find the 'Email Subscription Popup' plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to version 1.2.21
  5. 5. Alternatively, manually download version 1.2.21 from the WordPress plugin repository or the vendor's website
  6. 6. Deactivate the existing plugin, then delete it, and install the updated version
  7. 7. After updating, test the subscription form functionality to ensure it works correctly
  8. 8. Clear any caching plugins or server-side caches to ensure the updated plugin is served

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

Fix this in Email Subscription Popup Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-27960 — 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-27960 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