# CVE-2025-10682: TARIFFUXX <= 1.4 - Authenticated (Contributor+) SQL Injection via tariffuxx_configurator Shortcode

> Authenticated contributors can inject SQL via a shortcode to extract sensitive database information from the TARIFFUXX WordPress plugin.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-x63h-6rm3-fqx6

## What is CVE-2025-10682?

CVE-2025-10682 is a medium-severity SQL injection vulnerability in TARIFFUXX, published on 15 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2025-10682?


## How do I fix CVE-2025-10682?

No fix has been published for CVE-2025-10682 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-10682 being exploited?

There is no known exploitation of CVE-2025-10682 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10682 and fix it if it is affected.

What it is: CVE-2025-10682 is a medium-severity SQL injection vulnerability in TARIFFUXX, published on 15 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-10682 in the wild and no public exploit code.

Affected product: TARIFFUXX. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-10682/ (Markdown: https://insights.sbomify.com/CVE-2025-10682/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-10682
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-10682
- OSV: https://osv.dev/vulnerability/CVE-2025-10682

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-10682/
Summaries are generated and may contain mistakes; the official description above is the record.