dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-49326

HIGH · 7.6 CVSS v3.1 Published 2025-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 Ruben Garcia GamiPress gamipress allows SQL Injection.This issue affects GamiPress: from n/a through <= 7.4.5.

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 confidence

SQL injection vulnerability in the GamiPress WordPress plugin allows attackers to inject malicious SQL commands through unsanitized user input. The vulnerability exists in versions up to and including 7.4.5 and stems from improper neutralization of special elements in SQL queries.

MitigationUpdate GamiPress to the latest patched version beyond 7.4.5. If immediate patching is not possible, implement input validation at the application layer and review all database query paths for parameterized query usage.

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:H/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. Verify GamiPress plugin is installed
    Check the WordPress plugins directory for the gamipress folder: look in wp-content/plugins/ for a folder named gamipress, or log into WordPress admin and navigate to Plugins > Installed Plugins to confirm GamiPress appears in the list.
    Affected if The gamipress folder exists in wp-content/plugins/ or GamiPress appears in the WordPress admin plugins list.
  2. Identify the installed GamiPress version
    Access the WordPress admin panel, go to Plugins > Installed Plugins, find GamiPress, and note the version number displayed beneath the plugin name. Alternatively, open the main plugin file (wp-content/plugins/gamipress/gamipress.php) and locate the 'Version' header in the file comments.
    Affected if The version displayed is 7.4.5 or any version lower than 7.4.5.
  3. Confirm the plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify that GamiPress shows as 'Active' rather than 'Inactive'. The vulnerability is only exploitable when the plugin is actively loaded.
    Affected if GamiPress is activated and running on the WordPress site.
  4. Determine if custom query hooks exist
    Review any custom code, themes, or companion plugins that may interact with GamiPress database tables (prefixed with gamipress_). Check for custom hooks or callbacks that pass user-supplied input directly to WP_Query or $wpdb methods without prepare() or sanitization.
    Affected if Custom code passes $_GET, $_POST, or $_REQUEST parameters directly into GamiPress SQL queries without parameterized queries.

You are affected if GamiPress is installed, active, and running version 7.4.5 or lower, especially if custom code or user-facing features accept input that flows to database queries.

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 GamiPress to the latest patched version beyond 7.4.5. If immediate patching is not possible, implement input validation at the application layer and review all database query paths for parameterized query usage.

Recommended fix Moderate confidence

GamiPress 7.4.6 or latest stable release

  1. 1. Log in to the WordPress admin dashboard where GamiPress is installed.
  2. 2. Navigate to Plugins > Installed Plugins.
  3. 3. Locate the GamiPress plugin in the list.
  4. 4. If an update is available, click 'Update Now' to update GamiPress to the latest version.
  5. 5. After updating, verify the plugin is running on version 7.4.6 or later.
  6. 6. Test critical GamiPress functionality (points, achievements, ranks) to ensure the update did not break existing functionality.
Caveat Minor: Verify custom code or integrations with GamiPress hooks still function after upgrade, as with any plugin update

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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