SportspressWordPress extension · Themeboy
CVE-2020-13892
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 SportsPress plugin before 2.7.2 for WordPress allows XSS.
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 confidenceThe SportsPress WordPress plugin before version 2.7.2 contains a Cross-Site Scripting (XSS) vulnerability. This allows attackers to inject malicious scripts into web pages viewed by users of the affected plugin, potentially stealing session cookies, credentials, or performing actions on behalf of victims.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
SportspressWordPress extension
< 2.7.2CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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.
-
Confirm SportsPress plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins. Look for 'SportsPress' or 'Themeboy Sportspress' in the list of active plugins.Affected if SportsPress plugin appears in the installed plugins list
-
Identify the installed SportsPress versionIn the Plugins list, find the SportsPress entry. The version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file (usually in wp-content/plugins/sportspress/) for the 'Version' header in the plugin comment block.Affected if The displayed version number is less than 2.7.2 (e.g., 2.7.1, 2.7.0, 2.6.x, etc.)
-
Verify the plugin is activeIn WordPress admin > Plugins, confirm the SportsPress plugin shows as 'Active' rather than 'Inactive' or 'Must-Use'.Affected if Plugin status is Active
-
Check for XSS payload injection pointsReview the source code of SportsPress plugin files (particularly in includes/ or templates/ directories) for unsanitized output of user-supplied data in HTTP request parameters. Look for PHP code using $_GET, $_POST, or $_REQUEST without proper escaping functions like esc_html() or esc_attr().Affected if User input is reflected in page output without sanitization in plugin files
Your environment is affected if the SportsPress plugin is installed, active, and running a version lower than 2.7.2.
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.
From vendor data2.7.2
Update SportsPress plugin to version 2.7.2 or later. If immediate update is not possible, consider disabling the plugin or implementing WAF rules to filter malicious requests.
Fix this in Sportspress
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-13892 — 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-2020-13892 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