dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-39441

CRITICAL · 9.3 CVSS v3.1 Published 2026-06-15
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

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 Feed KuantoKusta for WooCommerce – Free <= 5.3 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 · high confidence

An unauthenticated SQL injection vulnerability exists in the Feed KuantoKusta for WooCommerce WordPress plugin versions 5.3 and below. Attackers can exploit this without authentication to inject malicious SQL queries, potentially allowing data exfiltration, privilege escalation, or complete database compromise.

MitigationUpgrade the Feed KuantoKusta for WooCommerce plugin to the latest version immediately. If patching is not possible, disable the plugin until an update is available. Additionally, review database logs for suspicious queries and consider rotating database credentials as a precautionary measure.

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. Identify if the Feed KuantoKusta for WooCommerce plugin is installed
    Log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Feed KuantoKusta for WooCommerce' in the list. Alternatively, check the wp-content/plugins/ directory for a folder containing 'kuantokusta' or 'feed-kuantokusta'.
    Affected if The plugin is installed and active in WordPress
  2. Determine the installed plugin version
    In the WordPress admin under Plugins > Installed Plugins, click on the plugin name to view its details, which typically displays the version number. Alternatively, open the main plugin file (usually feed-kuanto-kusta.php or similar in the plugin folder) and look for the 'Version:' header comment, or check the readme.txt file.
    Affected if The detected version is 5.3 or lower
  3. Compare against the affected version range
    Cross-reference the identified version number with the affected range. The vulnerability affects versions 5.3 and below. If your version is 5.3 or any version lower than 5.3, it falls within the affected range.
    Affected if The installed version is 5.3 or below (for example, 5.2, 5.1, 5.0, etc.)
  4. Inspect web server access logs for suspicious SQL injection patterns
    Review your web server access logs (typically found in /var/log/apache2/, /var/log/nginx/, or your hosting control panel) for unusual GET or POST requests to pages served by this plugin. Look for SQL keywords such as UNION, SELECT, INSERT, UPDATE, DELETE, or common SQL injection payloads in URL parameters.
    Affected if Unusual SQL-like patterns are found in requests targeting the plugin endpoints
  5. Review database query logs for unexpected SQL activity
    Check your MySQL or MariaDB slow query log or general query log (if enabled) for unusual or malicious-looking SQL queries that may indicate exploitation attempts. These logs are typically configured in my.cnf or my.ini and located in the MySQL data directory.
    Affected if Suspicious SQL queries appear in database logs that were not generated by known operations

If the Feed KuantoKusta for WooCommerce plugin is active and the installed version is 5.3 or below, the environment is affected by this unauthenticated SQL injection vulnerability.

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 Feed KuantoKusta for WooCommerce plugin to the latest version immediately. If patching is not possible, disable the plugin until an update is available. Additionally, review database logs for suspicious queries and consider rotating database credentials as a precautionary measure.

Recommended fix Moderate confidence

Latest available version of Feed KuantoKusta for WooCommerce (version > 5.3)

  1. 1. Backup your WordPress database and files before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Locate the 'Feed KuantoKusta for WooCommerce' plugin.
  4. 4. Check if the current version is 5.3 or lower.
  5. 5. If vulnerable, click 'Update Now' to install the latest available version, or manually download the latest version from the WordPress plugin repository.
  6. 6. After updating, verify the plugin is active and functioning correctly.
  7. 7. Test the feed generation functionality to ensure the update did not break existing functionality.
Caveat Review plugin changelog for any breaking changes between your current version and the latest release

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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