dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-10144

MEDIUM · 6.5 CVSS v3.1 Published 2025-11-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
The Perfect Brands for WooCommerce plugin for WordPress is vulnerable to time-based SQL Injection via the `brands` attribute of the `products` shortcode in all versions up to, and including, 3.6.2 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 Perfect Brands for WooCommerce plugin for WordPress contains a time-based SQL Injection vulnerability in the `products` shortcode's `brands` attribute. The plugin fails to properly escape user-supplied input and does not use prepared statements when constructing SQL queries, allowing authenticated attackers with Contributor-level access or higher to inject malicious SQL queries and extract sensitive data from the database.

MitigationUpdate the plugin to version 3.6.3 or later, which includes proper input escaping and prepared statements. If no update is available, implement output escaping on the `brands` parameter and refactor the SQL query to use $wpdb->prepare() with placeholder variables.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Perfect Brands for WooCommerce' in the installed plugins list, or check the file system at wp-content/plugins/perfect-brands-for-woocommerce/ for the plugin directory
    Affected if The plugin is not installed or has been removed entirely
  2. Identify installed version
    In WordPress admin > Plugins, find Perfect Brands for WooCommerce and read the version number displayed beneath the plugin name. Alternatively, check the main plugin file (usually perfect-brands-for-woocommerce.php) for the 'Version:' header in the plugin comments
    Affected if The installed version is lower than 3.6.3 (the fixed release)
  3. Check for vulnerable shortcode usage
    Search WordPress posts, pages, and widget content for the shortcode [products brand="..."] or [pwb-brand brand="..."], or use a search in the wp_posts database table for occurrences containing these shortcode patterns with the brands attribute
    Affected if The shortcode with the brands attribute is present in published content and the plugin version is below 3.6.3
  4. Verify user role permissions
    In WordPress admin > Users, review which users have Contributor-level access or higher. Contributors can execute the vulnerable shortcode through the front-end even without admin access
    Affected if There are users with Contributor, Author, Editor, or Administrator roles, making the attack surface active
  5. Inspect SQL query behavior (optional)
    Enable WordPress debug logging (wp-config.php: define( 'WP_DEBUG', true )) and monitor database queries when the shortcode is rendered with a brands parameter, or use a plugin like Query Monitor to inspect the actual SQL being executed
    Affected if The SQL query shows unsanitized brand parameter values being directly concatenated rather than using $wpdb->prepare() with placeholders

A user is affected if Perfect Brands for WooCommerce is installed at a version below 3.6.3 AND the products shortcode with a brands attribute is being used on the site, allowing any authenticated Contributor-level user to inject SQL through that parameter.

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 the plugin to version 3.6.3 or later, which includes proper input escaping and prepared statements. If no update is available, implement output escaping on the `brands` parameter and refactor the SQL query to use $wpdb->prepare() with placeholder variables.

Recommended fix Moderate confidence

Upgrade to the latest version of Perfect Brands for WooCommerce (version higher than 3.6.2)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate 'Perfect Brands for WooCommerce' in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version that includes the security fix
  5. 5. After updating, verify the plugin is working correctly by visiting a page with the products shortcode
  6. 6. Confirm the brands attribute in the shortcode works correctly (e.g., [products brands='brand-slug'])

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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