dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-48874

HIGH · 8.5 CVSS v3.1 Published 2026-06-15
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
Subscriber SQL Injection in GamiPress <= 7.8.7 versions.

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 GamiPress plugin versions 7.8.7 and below allows authenticated users with Subscriber role to inject malicious SQL queries through unspecified input parameters, potentially enabling unauthorized data access or database manipulation.

MitigationUpdate GamiPress to a version newer than 7.8.7; as an interim control, consider restricting or auditing subscriber-level user capabilities until the patch is applied.

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 GamiPress plugin is installed
    Navigate to WordPress admin dashboard > Plugins and look for GamiPress in the list of installed plugins, or check the /wp-content/plugins/gamipress/ directory exists on the server
    Affected if GamiPress is not installed on the WordPress site
  2. Identify installed GamiPress version
    In WordPress admin, go to Plugins > Installed Plugins > GamiPress and read the version number displayed below the plugin name; alternatively, check the version field in the plugin's main PHP file header at /wp-content/plugins/gamipress/gamipress.php
    Affected if The installed version is 7.8.7 or lower
  3. Check for Subscriber-level users
    In WordPress admin, go to Users > All Users and review the Role column for any accounts assigned the Subscriber role; use bulk actions or search to filter by Subscriber role
    Affected if There are active user accounts with Subscriber role who can log in
  4. Review web server and database logs for SQL errors
    Examine server error logs (often in /var/log/ or via hosting control panel) and any SQL query logs for suspicious SQL syntax errors or unusual queries originating from the GamiPress plugin endpoints, particularly around any user input fields
    Affected if SQL error messages or malformed SQL queries are found in logs related to GamiPress functionality
  5. Audit GamiPress activity logs if available
    If GamiPress activity logs or event logging is enabled, review recent entries for any unexpected or unauthorized database operations triggered by Subscriber-level users
    Affected if Activity logs show database operations performed by users with Subscriber role

Your environment is affected if GamiPress is installed with version 7.8.7 or lower AND there are active Subscriber-role users who could exploit the SQL injection via unspecified input fields in the plugin.

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 GamiPress to a version newer than 7.8.7; as an interim control, consider restricting or auditing subscriber-level user capabilities until the patch is applied.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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