dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-15368

HIGH · 8.8 CVSS v3.1 Published 2026-02-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 SportsPress plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 2.7.26 via shortcodes 'template_name' attribute. This makes it possible for authenticated attackers, with contributor-level and above permissions, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where php file type can be uploaded and included.

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 SportsPress WordPress plugin contains a Local File Inclusion vulnerability in its shortcode handler via the 'template_name' attribute. Authenticated users with contributor-level or higher permissions can supply path traversal sequences (e.g., ../../../../wp-config.php) to include and execute arbitrary PHP files on the server, enabling code execution and data exfiltration.

MitigationUpdate SportsPress to the latest patched version. Until then, restrict or disable the sp_events shortcode for untrusted users and audit contributor-level accounts.

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify SportsPress plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate SportsPress. Note the installed version number.
    Affected if SportsPress plugin is active and installed, regardless of version (vulnerability exists in unpatched versions)
  2. Check the SportsPress version against the patched release
    Compare your installed version number to the vendor's official patch release. The vendor released a fix after the vulnerability disclosure.
    Affected if Running any version prior to the vendor's patched release
  3. Identify contributor-level or higher user accounts
    In WordPress admin, go to Users and review roles. Contributor, Author, Editor, and Administrator roles all have permissions >= contributor level.
    Affected if At least one user account has contributor-level permissions or higher
  4. Confirm sp_events shortcode is available
    Test if [sp_events] shortcode is functional by creating a test post/page with just that shortcode and viewing it, or check if the shortcode is registered in the codebase.
    Affected if The sp_events shortcode is registered and accessible to authenticated users
  5. Verify template_name shortcode attribute is processed
    Test the shortcode with a template_name parameter (e.g., [sp_events template_name="test"]) to confirm the attribute is accepted and processed by the plugin.
    Affected if The template_name attribute is accepted and processed by the shortcode handler

User is affected if SportsPress plugin is installed with an unpatched version, and at least one contributor-level or higher user account exists with access to the sp_events shortcode that processes the template_name attribute.

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 SportsPress to the latest patched version. Until then, restrict or disable the sp_events shortcode for untrusted users and audit contributor-level accounts.

Recommended fix Moderate confidence

Latest available version of SportsPress from WordPress plugin repository (version higher than 2.7.26)

  1. 1. Check current SportsPress plugin version in WordPress admin under Plugins > Installed Plugins
  2. 2. Navigate to Plugins > Add New > Upload Plugin (or check WordPress plugin repository for latest version)
  3. 3. Download/install the latest version of SportsPress from the official WordPress plugin repository
  4. 4. Before activating, backup the WordPress database and files
  5. 5. Deactivate the current SportsPress plugin
  6. 6. Upload and activate the new version
  7. 7. Verify the shortcode functionality works correctly after upgrade
  8. 8. Ensure contributor-level users should be reviewed - consider limiting their permissions if not strictly required
Caveat Minor/feature updates between versions should not cause breaking changes; always test in staging first

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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