dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-22335

HIGH · 8.5 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
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
Subscriber SQL Injection in WooCommerce Frontend Manager – Ultimate < 6.7.7 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

SQL injection vulnerability in WooCommerce Frontend Manager – Ultimate plugin versions below 6.7.7 allows authenticated subscribers to inject malicious SQL queries through unsanitized input fields in the frontend interface, potentially enabling unauthorized data access, modification, or deletion from the WordPress database.

MitigationUpdate WooCommerce Frontend Manager – Ultimate to version 6.7.7 or later to patch the SQL injection vulnerability; if immediate update is not possible, consider disabling the plugin until the patch can be applied.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Check installed plugin version
    Navigate to WordPress admin > Plugins > WooCommerce Frontend Manager - Ultimate and view the version number displayed, or query the plugins database table for the version value
    Affected if version number is below 6.7.7
  2. Verify plugin is active
    Check WordPress plugins admin page or database wp_options table for active_plugins option to confirm WooCommerce Frontend Manager - Ultimate is currently enabled
    Affected if plugin is active and version is below 6.7.7
  3. Confirm subscriber user role exists
    Check WordPress users admin page or wp_users table to see if any users with subscriber role exist in the system
    Affected if subscriber-level users exist and plugin version is below 6.7.7
  4. Identify frontend input access points
    Review the WooCommerce Frontend Manager settings to determine which frontend forms or input fields are accessible to subscriber-level users (such as frontend product submission, review forms, or user dashboard interfaces)
    Affected if subscriber users can access frontend input forms and plugin version is below 6.7.7

User is affected if WooCommerce Frontend Manager - Ultimate plugin version is below 6.7.7, the plugin is active, and subscriber-level accounts exist with access to frontend input fields.

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

Update WooCommerce Frontend Manager – Ultimate to version 6.7.7 or later to patch the SQL injection vulnerability; if immediate update is not possible, consider disabling the plugin until the patch can be applied.

Recommended fix Moderate confidence

WooCommerce Frontend Manager – Ultimate version 6.7.7 or later

  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 'WooCommerce Frontend Manager – Ultimate' in the plugin list.
  4. 4. Check the current installed version number.
  5. 5. If the installed version is less than 6.7.7, update the plugin to version 6.7.7 or later.
  6. 6. Alternatively, you can update via WordPress.org plugin repository or FTP by downloading the latest version from the WordPress plugin directory.
  7. 7. After updating, verify the fix by testing subscriber-level user functionality that interacts with the frontend manager.
  8. 8. Ensure your WordPress installation and WooCommerce are also kept up to date.

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-2026-22335 — 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-22335 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