dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-59533

CRITICAL · 9.3 CVSS v3.1 Published 2026-07-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 3 weeks old

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
Unauthenticated SQL Injection in Relevanssi Light <= 1.2.2 versions.

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

An unauthenticated SQL injection vulnerability exists in the Relevanssi Light WordPress plugin versions 1.2.2 and below. Attackers can exploit this by sending malicious SQL payloads through input parameters without requiring any authentication, potentially allowing complete database compromise.

MitigationUpdate Relevanssi Light to the latest patched version immediately. If no patched version 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
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/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 Relevanssi Light plugin is installed
    Inspect the WordPress plugins directory (wp-content/plugins/) for the Relevanssi Light folder, or check the installed plugins list in the WordPress admin dashboard.
    Affected if The Relevanssi Light plugin folder exists or the plugin appears in the WordPress plugin list.
  2. Identify the installed version
    Open the main plugin file (usually relevanssi-light.php or similar) in the plugin directory and locate the version declaration in the plugin header comment, or view the version in the WordPress plugins admin page.
    Affected if The version number found is 1.2.2 or lower.
  3. Verify search functionality is active
    Test if the site search feature is functional and publicly accessible by performing a test search query on the WordPress site, or check if Relevanssi Light is enabled in the plugin settings.
    Affected if The search functionality is enabled and responds to queries without authentication.
  4. Confirm the plugin handles search queries
    Review the plugin settings in WordPress admin to verify Relevanssi Light is configured to handle site search, or inspect the site search behavior to confirm the plugin is processing search requests.
    Affected if Relevanssi Light is actively processing search queries on the site.

A site is affected if Relevanssi Light version 1.2.2 or below is installed, active, and processing search queries without authentication.

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

Update Relevanssi Light to the latest patched version immediately. If no patched version is available, disable the plugin until a fix is released.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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