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

CVE-2025-47508

HIGH · 7.5 CVSS v3.1 Published 2025-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Ruben Garcia GamiPress gamipress allows PHP Local File Inclusion.This issue affects GamiPress: from n/a through <= 7.3.7.

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 confidence

Local File Inclusion vulnerability in the GamiPress WordPress plugin allows attackers to include arbitrary local PHP files via improper input validation. This can lead to exposure of sensitive files or potentially remote code execution depending on server configuration.

MitigationUpdate GamiPress to the latest version beyond 7.3.7. Review server logs for signs of exploitation and consider restricting file inclusion paths as a defense-in-depth measure.

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 checks

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

  1. Confirm GamiPress plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a gamipress folder, or view installed plugins in WordPress admin under Plugins > Installed Plugins
    Affected if GamiPress plugin is present in the WordPress installation
  2. Identify installed GamiPress version
    View the plugin version in the WordPress admin under Plugins > Installed Plugins > GamiPress, or inspect the plugin header in the main plugin file (usually gamipress.php) or in readme.txt
    Affected if The installed version is lower than 7.3.7 (versions 7.3.7 and below are affected)
  3. Locate the vulnerable file inclusion endpoint
    Review the GamiPress plugin files for code that handles file path parameters, typically in admin or public-facing PHP files that use include/require with user-supplied input
    Affected if The plugin contains file inclusion code that uses unsanitized input from request parameters
  4. Check for signs of exploitation in access logs
    Search web server access logs (Apache error.log, Nginx access.log) for suspicious request patterns targeting the GamiPress plugin with directory traversal sequences (e.g., ../../) or direct file path references
    Affected if Log entries show LFI attempt patterns targeting GamiPress endpoints
  5. Verify WordPress configuration hardening
    Review the wp-config.php file for DISALLOW_FILE_MODELS constant or other security restrictions, and check if the web server has read access to sensitive system files outside the web root
    Affected if The server configuration allows the web user to read sensitive files that could be included via LFI

You are affected if GamiPress is installed with a version lower than 7.3.7 and the vulnerable file inclusion functionality is accessible to attackers.

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 GamiPress to the latest version beyond 7.3.7. Review server logs for signs of exploitation and consider restricting file inclusion paths as a defense-in-depth measure.

Recommended fix Moderate confidence

GamiPress version 7.3.8 or latest stable release

  1. 1. Backup your WordPress site and database before making any changes
  2. 2. Update the GamiPress plugin to the latest available version (7.3.8 or later)
  3. 3. Verify the update was successful by checking the plugin version in WordPress admin
  4. 4. Test that all GamiPress functionality (achievements, points, ranks) continues to work correctly
  5. 5. Clear any caching mechanisms if used

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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