dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-67999

HIGH · 7.6 CVSS v3.1 Published 2025-12-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Stefano Lissa Newsletter newsletter allows Blind SQL Injection.This issue affects Newsletter: from n/a through <= 9.0.9.

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 Newsletter plugin for WordPress by Stefano Lissa contains a Blind SQL Injection vulnerability. An attacker can inject malicious SQL queries through unsanitized input parameters in the newsletter component, allowing them to extract data from the database indirectly by observing application behavior differences between true and false conditions.

MitigationUpgrade the Newsletter plugin to version 9.0.10 or later, which contains the patched code that properly sanitizes input parameters to prevent SQL injection.

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Newsletter plugin is installed
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, or inspect the wp-content/plugins directory for a folder named 'newsletter' or similar
    Affected if The Newsletter plugin by Stefano Lissa is present in the WordPress installation
  2. Identify installed plugin version
    Open the main plugin file (typically newsletter/index.php or newsletter/plugin.php) and locate the version header in the plugin comments, or check the Versions tab in WordPress plugin repository if manually installed
    Affected if The version cannot be determined or is displayed as a version prior to 9.0.10
  3. Compare version against patched release
    Review the identified version number and compare it numerically to 9.0.10, noting that any version below 9.0.10 (including 9.0.9, 9.0.8, older major branches like 8.x, 7.x, etc.) falls within the vulnerable range
    Affected if The installed version is lower than 9.0.10 (for example: 9.0.9, 9.0.5, 8.x series, or any earlier release)
  4. Verify plugin is actively processing newsletter form submissions
    Check if the Newsletter plugin is enabled and its form shortcode or widget is published on any page or post, as the vulnerability requires user-supplied input to reach the vulnerable component
    Affected if The plugin is active and exposed through a public-facing form, subscription block, or signup widget

A user is affected if the Newsletter plugin for WordPress by Stefano Lissa is installed with any version prior to 9.0.10 and the newsletter subscription component is accessible to users or attackers.

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 the Newsletter plugin to version 9.0.10 or later, which contains the patched code that properly sanitizes input parameters to prevent SQL injection.

Recommended fix Moderate confidence

Newsletter plugin version 9.0.10 or later (check official WordPress plugin repository or vendor for exact patched release)

  1. Check the WordPress plugin repository or the developer's official site for the latest version of the Newsletter plugin
  2. Confirm that version 9.0.10 or later is available as the patched release
  3. Backup your WordPress site database and files before updating
  4. Update the Newsletter plugin to the latest available version through WordPress admin or via wp-cli: wp plugin update newsletter
  5. Verify the update was successful and the plugin is functioning correctly
Caveat Review plugin changelog for any breaking changes between your current version and the new version

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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