dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-3107

MEDIUM · 6.5 CVSS v3.1 Published 2025-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
The Newsletters plugin for WordPress is vulnerable to time-based SQL Injection via the ‘orderby' parameter in all versions up to, and including, 4.9.9.8 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 confidence

The Newsletters plugin for WordPress is vulnerable to time-based SQL injection via the 'orderby' parameter in versions up to 4.9.9.8. The vulnerability stems from insufficient escaping of user-supplied input combined with lack of prepared statements in the SQL query, allowing authenticated attackers with Contributor-level access to inject malicious SQL queries.

MitigationUpgrade to version 4.9.9.9 or later, which implements proper parameter escaping and prepared statements for the 'orderby' parameter.

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Check if Newsletters plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Newsletters' or inspect the file /wp-content/plugins/newsletters-lite/plugin.php and look for the version constant
    Affected if Plugin is not installed or not found, then not affected
  2. Identify the installed plugin version
    In the plugin list within WordPress admin, note the version number displayed under the plugin name, or open /wp-content/plugins/newsletters-lite/plugin.php and search for a line containing 'version' or 'VERSION'
    Affected if Version is 4.9.9.8 or lower (any version up to and including 4.9.9.8)
  3. Check for Contributor-level user accounts
    In WordPress admin, go to Users and review the role assigned to each user; or query the wp_usermeta table for users with 'wp_capabilities' containing 'contributor'
    Affected if At least one user account has Contributor role or higher (Author, Editor, Administrator) because these roles can exploit the vulnerability
  4. Verify the orderby parameter handling (optional manual check)
    If you have access to the plugin source, examine the file handling the front-end listing (commonly templates or class files) for usage of the 'orderby' parameter in SQL queries without prepare() statements
    Affected if The code uses $_GET['orderby'] or $_POST['orderby'] directly in SQL without $wpdb->prepare() or proper escaping

You are affected if the Newsletters plugin is installed with version 4.9.9.8 or lower AND you have user accounts with Contributor-level access or higher.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 4.9.9.9 or later, which implements proper parameter escaping and prepared statements for the 'orderby' parameter.

Recommended fix Moderate confidence

Latest version of the Newsletters plugin (newer than 4.9.9.8)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Newsletters' plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Alternatively, download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin is functioning normally

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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