Email Subscription PopupWordPress extension · I13websolution
CVE-2023-30489
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 · uneditedUnauth. Reflected Cross-Site Scripting (XSS) vulnerability in I Thirteen Web Solution Email Subscription Popup plugin <= 1.2.16 versions.
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 confidenceUnauthenticated reflected cross-site scripting (XSS) vulnerability in the Email Subscription Popup plugin by I Thirteen Web Solution allows attackers to inject malicious JavaScript via unsanitized user input that gets reflected back in the HTTP response without proper encoding.
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
<= 1.2.16CVSS 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.
-
Confirm plugin installation and versionAccess WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate 'Email Subscription Popup' by I Thirteen Web Solution, and note the version number displayed. Alternatively, check the plugin's main PHP file (usually in wp-content/plugins/email-subscription-popup/) for the 'Version' header in the plugin comment block.Affected if Version is 1.2.16 or lower
-
Verify plugin is activeIn WordPress admin under Plugins > Installed Plugins, confirm the Email Subscription Popup plugin shows as 'Active'. Reflected XSS requires the vulnerable code to be loaded and processing requests.Affected if Plugin is active and handling HTTP requests
-
Identify the subscription form endpointInspect the frontend of your WordPress site for the email subscription popup form. View the page source to find the form's action URL (typically contains 'email-subscription-popup' or similar path). Common paths include /wp-admin/admin-ajax.php or a dedicated submission handler.Affected if A subscription form endpoint exists and is accessible without authentication
-
Test for reflected XSS in form parametersUse a browser developer tool or curl to submit a crafted request to the subscription endpoint with a test payload in the email/name parameter (e.g., <script>alert('XSS')</script>). Inspect the HTTP response to see if the payload is reflected unencoded.Affected if The submitted input is reflected in the response without HTML encoding (visible as raw <script> tags or unescaped characters)
Your environment is affected if the Email Subscription Popup plugin is installed, active, version 1.2.16 or lower, and user-submitted input in the subscription form is reflected in responses without proper HTML encoding.
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 version newer than 1.2.16, or implement proper input sanitization and output encoding on the vulnerable parameter(s) to prevent script injection.
Fix this in Email Subscription Popup
Scoped from the published advisory
- Consultation1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30489 — 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-2023-30489 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