dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-32574

HIGH · 8.5 CVSS v3.1 Published 2025-07-16
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in mojoomla WPGYM allows SQL Injection. This issue affects WPGYM: from n/a through 65.0.

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 the WPGYM (WordPress Gym Management) plugin allows attackers to inject malicious SQL commands through unsanitized user input. This could allow unauthorized database access, data exfiltration, or manipulation of gym member data.

MitigationUpdate WPGYM to the latest version immediately. If no patch is available, disable the plugin until a fix is released. Implement parameterized queries or proper input sanitization in the meantime.

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. Confirm WPGYM plugin installation
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and search for 'WPGYM' or 'WordPress Gym Management' in the list
    Affected if WPGYM plugin is present in the installed plugins list
  2. Determine WPGYM version
    In the Plugins list, click on the WPGYM plugin name to view the details popup, or access the main plugin file at wp-content/plugins/wpgym/index.php (or similar main file) and locate the Version header comment
    Affected if The installed version matches or predates the vulnerable version range listed in the CVE advisory
  3. Verify plugin is active
    In Plugins > Installed Plugins, check if WPGYM displays an 'Active' status or has the active toggle enabled
    Affected if The plugin is currently active on the WordPress site
  4. Identify SQL input handling
    Review plugin PHP files in wp-content/plugins/wpgym/ for direct use of $_GET, $_POST, or $_REQUEST variables in SQL queries without $wpdb->prepare() or parameterized query functions
    Affected if The plugin contains code that passes user-supplied input directly into SQL queries without sanitization

Environment is affected if WPGYM plugin is installed, active, runs an unpatched version, and processes user input through SQL queries without proper sanitization.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WPGYM to the latest version immediately. If no patch is available, disable the plugin until a fix is released. Implement parameterized queries or proper input sanitization in the meantime.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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