# CVE-2025-54026: WordPress GymBase Theme Classes plugin <= 1.4 - SQL Injection Vulnerability

> An SQL injection vulnerability in the GymBase Theme Classes plugin allows attackers to read or modify database contents.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L`)
- **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:** 16 Jul 2025
- **Updated:** 13 May 2026
- **Also known as:** GHSA-8g79-jxg5-457m

## What is CVE-2025-54026?

CVE-2025-54026 is a high-severity SQL injection vulnerability in QuanticaLabs GymBase Theme Classes, published on 16 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in QuanticaLabs GymBase Theme Classes gymbase_classes allows SQL Injection.This issue affects GymBase Theme Classes: from n/a through <= 1.4.

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

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


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

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

## Is CVE-2025-54026 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-54026 is a high-severity SQL injection vulnerability in QuanticaLabs GymBase Theme Classes, published on 16 Jul 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-54026 in the wild and no public exploit code.

Affected product: QuanticaLabs GymBase Theme Classes. 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-54026/ (Markdown: https://insights.sbomify.com/CVE-2025-54026/index.md)
```

## Sources

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

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