dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-6929

HIGH · 7.5 CVSS v3.1 Published 2026-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
The JoomSport – for Sports: Team & League, Football, Hockey & more plugin for WordPress is vulnerable to time-based blind SQL Injection via the 'sortf' parameter in all versions up to, and including, 5.7.7 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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

The JoomSport WordPress plugin versions up to 5.7.7 contains a time-based blind SQL injection vulnerability in the 'sortf' parameter. Due to insufficient input sanitization and lack of prepared statements in the underlying SQL query, unauthenticated attackers can inject arbitrary SQL commands to exfiltrate sensitive data from the database.

MitigationUpdate the JoomSport plugin to version 5.7.8 or later which addresses the improper escaping and implements proper prepared statements for the 'sortf' parameter.

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 JoomSport plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, or check for /wp-content/plugins/joomsport-sports-league-results-management/ directory on the server
    Affected if The JoomSport plugin appears in the list of installed plugins
  2. Determine installed JoomSport version
    In WordPress admin, go to Plugins > Installed Plugins > JoomSport and read the version number displayed, or check the plugin's main PHP file for the 'Version' header comment
    Affected if Version displayed is 5.7.7 or lower
  3. Verify the 'sortf' parameter is exposed
    Inspect HTTP requests made to JoomSport-enabled pages (typically sports league/team pages) and look for URLs containing the 'sortf' parameter, or test by adding ?sortf=1 to any JoomSport page URL
    Affected if The 'sortf' parameter is accepted and processed by the plugin without error or filtering
  4. Check if the plugin is accessible to unauthenticated users
    Test accessing JoomSport public pages while logged out, or attempt a simple time-based test with ?sortf=1 AND SLEEP(5)-- to observe response delay (careful: this is for detection only, not exploitation)
    Affected if The plugin functionality and 'sortf' parameter are accessible without authentication

You are affected if JoomSport plugin version 5.7.7 or lower is installed and the 'sortf' parameter is accessible, regardless of authentication status.

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 the JoomSport plugin to version 5.7.8 or later which addresses the improper escaping and implements proper prepared statements for the 'sortf' parameter.

Recommended fix Moderate confidence

Version higher than 5.7.8 (check WordPress plugin repository for latest stable release)

  1. 1. Update the JoomSport plugin to the latest available version from the WordPress plugin repository
  2. 2. Navigate to WordPress admin dashboard > Plugins
  3. 3. Locate JoomSport – for Sports: Team & League, Football, Hockey & more
  4. 4. If an update is available, click 'Update Now'
  5. 5. After updating, verify the site still functions correctly
Caveat Minor: Review any plugin settings after upgrade as default configurations may have changed in newer versions

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 / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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