CVE-2026-13010
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 · uneditedThe JoomSport – for Sports: Team & League, Football, Hockey & more plugin for WordPress is vulnerable to time-based SQL Injection via 'event' Shortcode Attribute in all versions up to, and including, 5.7.9 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 shortcode can be embedded in posts or pages by Contributor-level users, making this exploitable by any authenticated user with at least that role.
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 confidenceThe JoomSport WordPress plugin fails to properly sanitize the 'event' shortcode attribute, allowing authenticated users with contributor-level access or higher to inject malicious SQL queries. The vulnerability stems from insufficient input escaping and lack of prepared statements in the SQL query handling, enabling time-based SQL injection to extract sensitive database information.
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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify JoomSport plugin installation and versionIn WordPress admin, go to Plugins > Installed Plugins and locate JoomSport. Note the version number displayed, or check the plugin's main PHP file header for the Version field.Affected if The installed version is 5.7.9 or lower (the vulnerability is present in versions up to 5.7.9; fixed in versions beyond 5.7.9).
-
Identify usage of the vulnerable 'event' shortcodeSearch your WordPress database or content for the shortcode pattern [joomsport_event ...] or [event ...] used by JoomSport. Use WP-CLI: 'wp db query "SELECT * FROM wp_posts WHERE post_content LIKE %event%"' or manually review posts/pages containing event-related content.Affected if The 'event' shortcode is present in any published post, page, or custom post type content, as this is the attack vector.
-
Audit user accounts with contributor-level or higher accessIn WordPress admin, go to Users > All Users and review the role column. Alternatively, query the wp_usermeta table: 'SELECT user_id, meta_value FROM wp_usermeta WHERE meta_key = "wp_capabilities" AND meta_value LIKE "%contributor%" OR meta_value LIKE "%author%" OR meta_value LIKE "%editor%" OR meta_value LIKE "%administrator%"'.Affected if There are user accounts with contributor, author, editor, or administrator roles, as these roles can exploit the SQL injection via the shortcode.
-
Review database for signs of SQL injection exploitationExamine the wp_posts and wp_options tables for suspicious patterns, particularly time-based sleep() commands or unusual data exfiltration attempts in recent entries. Check query logs if available: 'SELECT * FROM wp_posts WHERE post_content LIKE "%sleep%" OR post_content LIKE "%benchmark%"'.Affected if Unusual patterns or time-delayed queries are found in recent database entries, indicating potential exploitation attempts.
-
Check shortcode handler source code for prepared statementsLocate the JoomSport plugin shortcode handler file (typically in includes/shortcodes/ or similar) and inspect the function handling the 'event' attribute. Look for $wpdb->prepare() usage. If the code directly interpolates the event parameter into SQL without prepare(), the vulnerability exists.Affected if The shortcode handler does not use $wpdb->prepare() or parameterized queries for the 'event' attribute, confirming the vulnerability is present in the code.
You are affected if the JoomSport plugin version is 5.7.9 or lower, the 'event' shortcode is in use, and you have users with contributor-level or higher access, or if you detect signs of SQL injection in your database.
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.
dbcve · scopedUpdate the JoomSport plugin to a version beyond 5.7.9 when available. Until a patch is released, review and remove any shortcode implementations using the 'event' attribute and consider deploying a WAF to filter SQL injection attempts.
Update to the latest available version of JoomSport (version higher than 5.7.9)
- 1. Log in to the WordPress admin dashboard with administrator privileges.
- 2. Navigate to Plugins > Installed Plugins.
- 3. Locate the JoomSport plugin in the list.
- 4. If an update is available, click 'Update Now' to install the latest version.
- 5. Alternatively, download the latest version from the WordPress Plugin Repository and upload it via Plugins > Add New > Upload Plugin.
- 6. After updating, verify the plugin status shows the current version.
- 7. Test that the JoomSport shortcodes function correctly on the site.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13010 — 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-2026-13010 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