CVE-2025-46463
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 Yamna Khawaja Mailing Group Listserv wp-mailing-group allows SQL Injection.This issue affects Mailing Group Listserv: from n/a through <= 3.0.4.
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 confidenceSQL injection vulnerability in the wp-mailing-group WordPress plugin allows attackers to inject malicious SQL commands through unsanitized user inputs in the mailing group listserv functionality, potentially allowing unauthorized data access or modification.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L
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.
-
Locate the wp-mailing-group plugin installationCheck the WordPress plugins directory (wp-content/plugins/) for the wp-mailing-group folder, or query the wp_plugins database table for the plugin slugAffected if The plugin folder or database entry exists - meaning the plugin is installed
-
Identify the installed plugin versionCheck the plugin's main PHP file header for the 'Version' tag, or query the wp_plugins database table for the version fieldAffected if The installed version is lower than the patched version released to address this SQL injection vulnerability
-
Verify the mailing group listserv feature is activeCheck the plugin's settings in WordPress admin under the plugin's configuration page, or inspect the wp_options table for plugin-specific settings related to listserv functionalityAffected if The listserv feature is enabled and configured with active mailing group settings
-
Confirm the plugin handles user input through web-facing formsInspect the plugin's PHP files for $_POST, $_GET, or $_REQUEST superglobal usage in files related to listserv handling, or check if public-facing forms exist that submit to plugin endpointsAffected if The plugin processes user-submitted data through web forms without evident sanitization
-
Review database query construction in plugin filesExamine PHP files in the plugin for direct SQL query construction using variables from user input (such as $wpdb->prepare with unsanitized parameters, or string concatenation into SQL statements)Affected if SQL queries incorporate user input without proper parameterization or escaping
A user is affected if the wp-mailing-group plugin is installed, the listserv feature is enabled, and the installed version predates the patched release for CVE-2025-46463.
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 the latest patched version once released. If no patch is available, disable the plugin or implement input validation and parameterized queries at all SQL touchpoints.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46463 — 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-2025-46463 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