# CVE-2022-35235: WordPress WPide plugin <= 2.6 - Authenticated Arbitrary File Read vulnerability

> Authenticated administrators can read arbitrary files on the server via a path traversal vulnerability in the WPide plugin.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/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:** 23 Aug 2022
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-q7xv-26r5-c2h7

## What is CVE-2022-35235?

CVE-2022-35235 is a medium-severity path traversal vulnerability in XplodedThemes WPIDE – File Manager & Code Editor (WordPress plugin), published on 23 Aug 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Authenticated (admin+) Arbitrary File Read vulnerability in XplodedThemes WPide plugin <= 2.6 at WordPress.

Weakness: CWE-552 (Files or Directories Accessible to External Parties), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2022-35235?

It affects 1 product.


Products: Xplodedthemes Wpide - File Manager \& Code Editor.

## How do I fix CVE-2022-35235?

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

## Is CVE-2022-35235 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-35235 and fix it if it is affected.

What it is: CVE-2022-35235 is a medium-severity path traversal vulnerability in XplodedThemes WPIDE – File Manager & Code Editor (WordPress plugin), published on 23 Aug 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-35235 in the wild and no public exploit code.

Affected product: XplodedThemes WPIDE – File Manager & Code Editor (WordPress plugin). 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-2022-35235/ (Markdown: https://insights.sbomify.com/CVE-2022-35235/index.md)
```

## Sources

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

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