# CVE-2026-103293: MPG < 4.2.3 - Editor+ Arbitrary File Read via Project Import

> Editors can read arbitrary server files via project import, exposing sensitive data to unauthenticated users.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Oct 2026
- **Updated:** 3 Oct 2026
- **Also known as:** GHSA-g2jh-6wh7-j7fj

## What is CVE-2026-103293?

CVE-2026-103293 is a medium-severity path traversal vulnerability in Unknown MPG, published on 3 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The MPG  WordPress plugin before 4.2.3 does not validate that the dataset source supplied when importing a project is a remote URL before treating it as a local filesystem path and copying that file into a publicly accessible uploads folder. This makes it possible for users with the Editor role and above to read the contents of arbitrary files on the server, with the copied file then retrievable by unauthenticated visitors.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


## How do I fix CVE-2026-103293?

No fix has been published for CVE-2026-103293 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-103293 being exploited?

There is no known exploitation of CVE-2026-103293 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-103293 and fix it if it is affected.

What it is: CVE-2026-103293 is a medium-severity path traversal vulnerability in Unknown MPG, published on 3 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-103293 in the wild and no public exploit code.

Affected product: Unknown MPG. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-103293/ (Markdown: https://insights.sbomify.com/CVE-2026-103293/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-103293
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-103293
- OSV: https://osv.dev/vulnerability/CVE-2026-103293

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-103293/
Summaries are generated and may contain mistakes; the official description above is the record.