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

CVE-2025-7721

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 JoomSport – for Sports: Team & League, Football, Hockey & more plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 5.7.3 via the task parameter. This makes it possible for unauthenticated attackers to include and execute arbitrary .php 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 types 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 JoomSport WordPress plugin versions up to 5.7.3 contains a Local File Inclusion vulnerability via the 'task' parameter. Unauthenticated attackers can exploit this to include and execute arbitrary .php files on the server, achieving remote code execution or bypassing access controls.

MitigationUpdate the JoomSport plugin to version 5.7.4 or later. As an immediate workaround, disable the plugin if not essential, or implement web application firewall rules to block directory traversal patterns in the task parameter.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 JoomSport plugin version
    In WordPress admin, go to Plugins > Installed Plugins > JoomSport and read the version number displayed, or inspect the plugin header in /wp-content/plugins/joomsport/joomsport.php
    Affected if The installed version is 5.7.3 or any lower version number
  2. Confirm plugin is active
    Check the WordPress plugins page to see if JoomSport shows as 'Active'
    Affected if The plugin is active and running
  3. Identify vulnerable parameter exposure
    Check if the JoomSport component is accessible on the frontend. The vulnerable URL pattern is /index.php?option=com_joomsport&task=YOUR_VALUE. Try accessing a non-existent task like /index.php?option=com_joomsport&task=test to see if the component loads without authentication
    Affected if The Joomsport component responds to requests without requiring authentication
  4. Test for LFI condition
    Attempt a safe test request including a known harmless file, such as /index.php?option=com_joomsport&task=../../../../../../../../etc/passwd (checking if the path traversal is processed). Monitor whether the server attempts to include the file or returns an error revealing path information
    Affected if The server reveals file paths or includes content from files outside the expected directory

You are affected if JoomSport plugin version is 5.7.3 or lower AND the component is active and accessible without authentication.

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 the JoomSport plugin to version 5.7.4 or later. As an immediate workaround, disable the plugin if not essential, or implement web application firewall rules to block directory traversal patterns in the task parameter.

Recommended fix High confidence

5.7.4 or later

  1. Update the JoomSport plugin to the latest available version from the WordPress plugin repository
  2. Navigate to Plugins > All Plugins in the WordPress admin dashboard
  3. Locate the JoomSport plugin and click 'Update Now' if an update is available
  4. Alternatively, download the latest version from plugins.trac.wordpress.org and upload it manually via Plugins > Add New > Upload Plugin
  5. Verify the update was successful by checking the plugin version after updating

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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