Email Posts To SubscribersWordPress extension · Gopiplus
CVE-2022-46818
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Gopi Ramasamy Email posts to subscribers allows SQL Injection.This issue affects Email posts to subscribers: from n/a through 6.2.
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 confidenceA critical SQL injection vulnerability exists in the Email posts to subscribers WordPress plugin (versions through 6.2). The plugin fails to properly sanitize user input before using it in SQL queries, allowing remote unauthenticated attackers to inject malicious SQL commands and potentially extract, modify, or delete database contents.
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 Posts To SubscribersWordPress extension
<= 6.2CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Verify the plugin is installedCheck the WordPress plugins directory for the email-posts-to-subscribers or gopiplus-email-posts-to-subscribers folder. In a standard WordPress installation, this would be at /wp-content/plugins/email-posts-to-subscribers/ or similar.Affected if The plugin folder exists in the WordPress plugins directory
-
Identify the installed plugin versionOpen the main plugin file (usually named similar to email-posts-to-subscribers.php) and locate the Version header in the plugin comment block at the top of the file. Compare this version number to the affected range (<= 6.2).Affected if The version listed is 6.2 or any earlier version
-
Confirm the plugin is activeLog into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Check if the Email posts to subscribers plugin shows as Active.Affected if The plugin appears as Active in the WordPress admin plugins list
-
Check for vulnerable query handlersIf you have file system access, examine the plugin's PHP files for direct usage of $wpdb->prepare, $wpdb->query, or similar database functions without proper prepare() calls. Look for files that handle subscriber data or email sending functionality.Affected if Database query code lacks proper prepared statement usage and processes user-supplied input
Your environment is affected if the Email posts to subscribers plugin is installed, active, and running version 6.2 or earlier, since the SQL injection vulnerability can be exploited by remote unauthenticated attackers through the plugin's input handling.
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 dataUpgrade the Email posts to subscribers plugin to version 6.3 or later. If no patch is available, disable the plugin until a fix is released. Alternatively, implement input validation and convert vulnerable database queries to use prepared statements.
Fix this in Email Posts To Subscribers
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46818 — 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-2022-46818 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