JoomSport <= 5.7.11 - Authenticated (Contributor+) SQL Injection via 'team_id' Shortcode Attribute
Impact
JoomSport WordPress plugin versions up to 5.7.11 have a SQL injection vulnerability via the 'team_id' shortcode attribute, allowing authenticated attackers with contributor-level access to extract sensitive database information. The issue is due to insufficient escaping and preparation of the user-supplied parameter. This affects the plugin when a season has no associated joomsport_tournament term.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
beardev · Wordfence
JoomSport – for Sports: Team & League, Football, Hockey & more
1 range
beardev · Wordfence
JoomSport – for Sports: Team & League, Football, Hockey & more
Compare with this publisher’s ranges. This does not inspect your installation.
affected
0 → through 5.7.11
semver versions
Other versions: unaffected
Original source description
The JoomSport – for Sports: Team & League, Football, Hockey & more plugin for WordPress is vulnerable to generic SQL Injection via the 'team_id' parameter in all versions up to, and including, 5.7.11 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with contributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The vulnerable code path is reached when the season has no associated joomsport_tournament term, which is the default state for newly created seasons.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-118192View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 2
Assigning organization
Additional data publisher
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.