dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-39496

HIGH · 7.6 CVSS v3.1 Published 2026-04-08
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 YayCommerce YayMail yaymail allows Blind SQL Injection.This issue affects YayMail: from n/a through <= 4.3.3.

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 confidence

A Blind SQL Injection vulnerability exists in the YayCommerce YayMail WordPress plugin (versions up to 4.3.3). The vulnerability allows unauthenticated attackers to inject malicious SQL queries through unsanitized input parameters, potentially enabling data exfiltration or database manipulation.

MitigationUpgrade YayMail to a patched version beyond 4.3.3 that includes proper input sanitization and parameterized queries. If no patch is available, disable the plugin until a fix is released.

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. Verify YayMail plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for YayMail, or check the /wp-content/plugins/ directory for a folder named yaymail or similar
    Affected if YayMail plugin is present in the WordPress installation
  2. Check installed YayMail version
    Navigate to Plugins > Installed Plugins > YayMail and view the version number displayed, or check the main plugin file header for the Version field
    Affected if The version is 4.3.3 or lower (any version through 4.3.3 is affected)
  3. Identify accessible SQL injection entry points
    Review the plugin endpoints that handle user input and interact with the database - the vulnerability allows injection through improper neutralization of SQL command elements
    Affected if Any YayMail functionality that processes unsanitized input and directly queries the database is reachable
  4. Examine web server and application logs for SQL injection attempts
    Search access logs for unusual SQL syntax patterns in YayMail-related requests, such as UNION SELECT, OR 1=1, or time-based blind SQL injection indicators like SLEEP()
    Affected if Suspicious SQL patterns are found in requests targeting YayMail endpoints

The environment is affected if YayMail plugin versions 4.3.3 or lower are installed and the plugin or its endpoints are accessible, regardless of authentication status.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade YayMail to a patched version beyond 4.3.3 that includes proper input sanitization and parameterized queries. If no patch is available, disable the plugin until a fix is released.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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