dbcve.org
GrandprixWordPress extension · Qodeinteractive

CVE-2025-49296

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-09
Fix available
A fix is available. Upgrade to 1.6.1 or later.
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
Path Traversal: '.../...//' vulnerability in Mikado-Themes GrandPrix grandprix allows PHP Local File Inclusion.This issue affects GrandPrix: from n/a through <= 1.6.

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

A path traversal vulnerability in Mikado-Themes GrandPrix theme allows remote attackers to manipulate file paths using the '.../...//' pattern to achieve PHP Local File Inclusion (LFI). This enables attackers to include and execute arbitrary PHP files from the server's filesystem, potentially leading to remote code execution (RCE). The vulnerability affects all versions through 1.6.

MitigationImmediately restrict file inclusion to trusted paths, implement strict input validation blocking traversal sequences ('..', '/'), and upgrade to a patched version if available. Additionally, disable allow_url_include in PHP configuration 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.

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
GrandprixWordPress extension
Affected:< 1.6.1

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. Locate GrandPrix theme installation
    Check your web server's theme directory (typically wp-content/themes/grandprix or wp-content/themes/grandprix-child) for the presence of GrandPrix theme files.
    Affected if The grandprix folder exists in your themes directory.
  2. Identify installed GrandPrix version
    Open the style.css file in the GrandPrix theme folder and look for the 'Version:' declaration in the theme header comment at the top. Alternatively, check theme.json if present.
    Affected if The version listed is below 1.6.1 (e.g., 1.6.0, 1.5.x, 1.0.x).
  3. Verify vulnerable file inclusion functions exist
    Search the theme PHP files (particularly in includes/ or functions.php) for include, include_once, require, or require_once statements that accept user input without strict validation.
    Affected if The theme contains file inclusion functions that process dynamic input without allowlist validation.
  4. Test for path traversal vulnerability
    If the theme exposes URL parameters for file inclusion (common in theme option pages or template files), send a request using the pattern '.../...//' followed by a known file path (e.g., ../../wp-config.php). Note: Only test on non-production systems or with explicit authorization.
    Affected if The application returns content from files outside the expected directory, confirming LFI is possible.
  5. Review web server access logs
    Examine HTTP access logs for requests containing '../' sequences or the specific pattern '.../...//' directed at the theme's PHP files.
    Affected if Such patterns appear in your logs targeting GrandPrix theme endpoints.

You are affected if the GrandPrix theme version is below 1.6.1 AND file inclusion functionality using unvalidated input is accessible on your site.

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
Upgrade available Upgrade to 1.6.1 or later
Fixed in 1.6.1
Interim mitigation

Immediately restrict file inclusion to trusted paths, implement strict input validation blocking traversal sequences ('..', '/'), and upgrade to a patched version if available. Additionally, disable allow_url_include in PHP configuration as a defense-in-depth measure.

Recommended fix High confidence

1.6.1

  1. Obtain GrandPrix theme version 1.6.1 from the official Mikado-Themes source
  2. Update the GrandPrix theme to version 1.6.1 through your WordPress dashboard or via FTP/SFTP file replacement
  3. Verify the theme version has been updated to 1.6.1

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

Fix this in Grandprix Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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