Email Subscribers \& NewslettersWordPress extension · Icegram
CVE-2019-14364
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 · uneditedAn XSS vulnerability in the "Email Subscribers & Newsletters" plugin 4.1.6 for WordPress allows an attacker to inject malicious JavaScript code through a publicly available subscription form using the esfpx_name wp-admin/admin-ajax.php POST parameter.
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 · high confidenceStored XSS vulnerability in WordPress plugin 'Email Subscribers & Newsletters' version 4.1.6 allows remote attackers to inject malicious JavaScript via the publicly accessible subscription form at wp-admin/admin-ajax.php using the unsanitized esfpx_name POST parameter.
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 Subscribers \& NewslettersWordPress extension
= 4.1.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify plugin installation and versionNavigate to WordPress admin dashboard, go to Plugins > Installed Plugins, locate 'Email Subscribers & Newsletters' or 'Icegram Email Subscribers & Newsletters' and note the installed version numberAffected if The plugin is installed and the version listed is exactly 4.1.6
-
Verify public subscription form is accessibleSend a POST request to /wp-admin/admin-ajax.php with action=esfpx_form_submit and include the esfpx_name parameter (e.g., curl -X POST http://TARGET/wp-admin/admin-ajax.php -d 'action=esfpx_form_submit&esfpx_name=test')Affected if The endpoint responds and accepts the esfpx_name parameter without authentication, meaning the subscription form is publicly exposed
-
Inspect stored subscription data for malicious contentAccess the WordPress database (via phpMyAdmin or mysql CLI) and query the plugin's subscription table for any esfpx_name entries containing script tags or suspicious JavaScript patterns (e.g., SELECT * FROM wp_esp_subscribers WHERE name LIKE '%<script%' OR name LIKE '%onload=%')Affected if Any records in the esfpx_name or equivalent name field contain unsanitized HTML/script tags that were successfully stored and could execute when viewed in the admin panel
You are affected if the Email Subscribers & Newsletters plugin version 4.1.6 is installed and the subscription form at admin-ajax.php is publicly accessible, allowing unsanitized esfpx_name input to be stored in the database.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate the plugin to a patched version and ensure all user inputs in subscription forms are properly sanitized before storage and output.
Fix this in Email Subscribers \& Newsletters
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14364 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-14364 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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