CVE
Mikado-Themes GrandPrix Core unauthenticated local file inclusion in WordPress plugin
Affects the Mikado-Themes GrandPrix Core WordPress plugin, version 1.0 and earlier. The checked facts list no vendor rating and no fixed version.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: The checked facts include no workaround or fixed version, so no specific mitigation can be given here. Follow the vendor's advisory for guidance until a fix is published.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.44% · 38th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 31/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
The GrandPrix Core plugin for WordPress, made by Mikado-Themes, contains a local file inclusion flaw that lets an attacker remotely, without logging in, make the software load and run files from the server's local file system. Exploiting it can expose or affect data on the server.
Original description
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Mikado-Themes GrandPrix Core grandprix-core allows PHP Local File Inclusion.This issue affects GrandPrix Core: from n/a through 1.0.
Who should check
Teams running the GrandPrix Core WordPress plugin version 1.0 or earlier, such as WordPress sites using the Mikado-Themes GrandPrix theme
“WordPress GrandPrix Core Plugin <= 1.0 is vulnerable to a high priority Local File Inclusion”
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.1/10CVSS 8.1, total technical impact per CISA
- No patch5/5No patch listed yet
What would change the score
- Would score about 76 if added to CISA KEV
- Would score about 71 if CISA's SSVC rates exploitation active
- Would score about 36 if advisories confirm default setups are exposed
What to do
Workaround: The checked facts include no workaround or fixed version, so no specific mitigation can be given here. Follow the vendor's advisory for guidance until a fix is published.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129091 (WordPress GrandPrix Core plugin <= 1.0 - Local File Inclusion vulnerability), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129091 (entry last updated 2026-11-16):
Affected:
- Mikado-Themes GrandPrix Core: through 1.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- GrandPrix Core WordPress plugin version 1.0 or earlier (source: https://patchstack.com/database/wordpress/plugin/grandprix-core/vulnerability/wordpress-grandprix-core-plugin-1-0-local-file-inclusion-vulnerability?_s_id=cve)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-129091 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129091 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://patchstack.com/database/wordpress/plugin/grandprix-core/vulnerability/wordpress-grandprix-core-plugin-1-0-local-file-inclusion-vulnerability?_s_id=cve
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129091
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129091"}.Timeline
- CVE published
- First seen by cve.now1 day
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- grandprix-core
through 1.0
Evidence 3
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129091
Is CVE-2026-129091 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The plugin has a Local File Inclusion flaw that lets attackers make the site load server files it should not. In some cases this can lead to a full site takeover.Source: patchstack.com
Which versions are affected by CVE-2026-129091?
grandprix-core: through 1.0.Source: cve.now feed data
Am I affected, and how do I check?
The checked facts list GrandPrix Core versions 1.0 and earlier for the WordPress plugin by Mikado-Themes. The installed version can be seen on the WordPress Plugins screen in the admin area.Source: patchstack.com
How do I fix CVE-2026-129091?
The checked facts name no fixed version and no vendor patch identifiers, so no upgrade target can be given. Check the vendor's advisory for a fixed release.Source: patchstack.com
What if there's no patch?
The checked facts include no workaround or fixed version, so no specific mitigation can be given here. Follow the vendor's advisory for guidance until a fix is published.Source: patchstack.com