CVE-2026-57749
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 · uneditedContributor Local File Inclusion in SportsPress Pro <= 2.7.29 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 confidenceLocal File Inclusion vulnerability in SportsPress Pro allows authenticated users with Contributor-level privileges to read arbitrary files from the server filesystem by manipulating file path parameters.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
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 Pro is installedCheck the WordPress plugins directory for the SportsPress Pro plugin folder, typically at /wp-content/plugins/sportspress-pro/, or look for SportsPress Pro in the WordPress admin plugins list.Affected if SportsPress Pro plugin is present on the WordPress site
-
Identify the installed SportsPress Pro versionOpen the main plugin file (sportspress-pro.php) and check the Version header in the plugin comment block, or query the wp_options table for the 'sportspress_pro_version' option if available.Affected if The version is 2.7.29 or earlier (no patched version beyond 2.7.29 is confirmed)
-
Verify contributor-level user accounts existNavigate to WordPress admin under Users > All Users and check for users with the Contributor role, or query the wp_usermeta table where meta_key = 'wp_capabilities' and meta_value contains 'contributor'.Affected if Any contributor-level user accounts are present on the site
-
Inspect file inclusion endpoints in SportsPressReview the SportsPress Pro plugin files for functions that accept file path parameters (such as include, require, fopen, file_get_contents with user-controlled input), typically in admin or public facing files that handle template or file loading.Affected if File inclusion functions with unsanitized path parameters are found in the plugin code
A site is affected if SportsPress Pro version 2.7.29 or earlier is installed AND contributor-level user accounts exist, allowing authenticated contributors to exploit file path manipulation in the plugin.
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 dataUpgrade SportsPress Pro to a version beyond 2.7.29. If no patched version is available, review and restrict contributor-level permissions and audit the plugin's file inclusion logic for proper path sanitization.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57749 — 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-57749 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