CVE-2025-32643
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in mojoomla WPGYM allows Blind 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 · moderate confidenceA blind SQL injection vulnerability in the mojoomla WPGYM WordPress plugin allows unauthenticated attackers to inject malicious SQL commands through unsanitized input parameters. The blind SQL injection nature means attackers infer database content through application response differences rather than seeing direct output. The CVSS 9.3 indicates severe potential impact including data exfiltration or complete database compromise.
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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if WPGYM plugin is installedNavigate to WordPress admin dashboard under Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a folder named wpgym, wpgym-pro, or similar WPGYM variationsAffected if The WPGYM plugin (by mojoomla) appears in the installed plugins list
-
Determine installed WPGYM versionIn WordPress admin, view the plugin details page to see the version number, or check the main plugin PHP file header for the 'Version' fieldAffected if The displayed version does not match the latest patched version from vendor (the vulnerability exists in unpatched versions)
-
Verify plugin is activeCheck the WordPress plugins admin page to confirm WPGYM status shows as 'Active'Affected if The plugin is active and publicly accessible to unauthenticated users
-
Identify vulnerable entry pointsReview plugin code for PHP files handling GET or POST parameters (such as id, gym_id, or similar parameters) that are used in SQL queries without prepare() or esc_sql() functionsAffected if Unsanitized user-supplied parameters are directly incorporated into SQL queries without prepared statements
If the WPGYM plugin is installed, active, running an unpatched version, and exposes unsanitized input parameters to unauthenticated users, the environment is affected by this blind SQL injection vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate WPGYM to the latest version to obtain the vendor patch. If no patch is available, implement parameterized queries or prepared statements for all database interactions and add input validation/sanitization at all user-supplied parameter entry points.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32643 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-32643 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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