dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-10682

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-15
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 TARIFFUXX plugin for WordPress is vulnerable to SQL Injection in versions up to, and including, 1.4. This is due to insufficient neutralization of user-supplied input used directly in SQL queries. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject additional SQL into queries and extract sensitive information from the database via a crafted id attribute in the 'tariffuxx_configurator' shortcode.

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 TARIFFUXX WordPress plugin (versions up to 1.4) contains a SQL Injection vulnerability in the tariffuxx_configurator shortcode handler. Authenticated users with Contributor-level access or higher can exploit an unsanitized 'id' parameter directly in SQL queries, allowing extraction of sensitive database information.

MitigationUpdate the TARIFFUXX plugin to version 1.5 or later, which should implement proper input sanitization and use prepared statements for database queries.

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. Verify TARIFFUXX plugin is installed
    Log into WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'TARIFFUXX' in the plugin list. Note the version number displayed.
    Affected if The TARIFFUXX plugin appears in the installed plugins list with a version number visible.
  2. Confirm installed version is vulnerable
    Compare the displayed plugin version to the affected range (versions up to and including 1.4). If the version shown is 1.4 or lower, the plugin is vulnerable.
    Affected if The installed version is 1.4 or lower (for example: 1.4, 1.3.2, 1.0).
  3. Identify usage of vulnerable shortcode
    Search WordPress content (posts, pages, widgets) for the shortcode [tariffuxx_configurator]. This can be done via WordPress admin search, or by querying the wp_posts table for the shortcode string.
    Affected if The shortcode [tariffuxx_configurator] is present in any post, page, or custom post type content.
  4. Check shortcode for id parameter
    Examine any found shortcode usage to see if an 'id' attribute is present, for example: [tariffuxx_configurator id="123"]. The vulnerable code processes this 'id' parameter directly in SQL.
    Affected if The shortcode includes an 'id' attribute with a value, such as [tariffuxx_configurator id="VALUE"].
  5. Assess user role exposure
    Navigate to Users > All Users in WordPress admin and review which users have Contributor-level access or higher. These roles can exploit the vulnerability.
    Affected if There are any user accounts assigned the Contributor, Author, Editor, or Administrator role.

A user is affected if they have TARIFFUXX plugin version 1.4 or lower installed AND the tariffuxx_configurator shortcode with an id parameter is in use, with at least one authenticated user having Contributor-level access or higher.

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 TARIFFUXX plugin to version 1.5 or later, which should implement proper input sanitization and use prepared statements for database queries.

Recommended fix Moderate confidence

Version 1.5 or later

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the TARIFFUXX plugin in the list
  4. Check the current version installed (should be 1.4 or lower)
  5. If an update is available, click 'Update Now' to update to the latest version
  6. Alternatively, download the latest version from wordpress.org/plugins/tariffuxx and upload manually via Plugins > Add New > Upload Plugin
  7. After update, verify the plugin is running version 1.5 or higher
Caveat Minor plugin version upgrade typically has no breaking changes

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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