# CVE-2018-16363: Cross-site scripting in n/a

> Cross-site scripting in WordPress File Manager plugin allows attackers to inject scripts via the lang parameter, potentially leading to session hijacking or code execution.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7gvh-pc64-w2xw

## What is CVE-2018-16363?

CVE-2018-16363 is a medium-severity cross-site scripting vulnerability in n/a, published on 7 Sep 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The mndpsingh287 File Manager plugin V2.9 for WordPress has XSS via the lang parameter in a wp-admin/admin.php?page=wp_file_manager request because set_transient is used in file_folder_manager.php and there is an echo of lang in lib\wpfilemanager.php.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2018-16363?

It affects 1 product.


Products: Filemanagerpro File Manager.

## How do I fix CVE-2018-16363?

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

## Is CVE-2018-16363 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-16363 exists.

Public exploit code:

- WordPress File Manager < 3.0 - Cross-Site Scripting (nuclei): http/cves/2018/CVE-2018-16363.yaml

## Other vulnerabilities in n/a

- [CVE-2020-25213](https://insights.sbomify.com/CVE-2020-25213/): WordPress File Manager Plugin Remote Code Execution (critical 10.0, exploited in the wild)
- [CVE-2018-25105](https://insights.sbomify.com/CVE-2018-25105/): File Manager <= 3.0 - Unauthenticated Arbitrary File Upload/Download (critical 9.8)
- [CVE-2024-8507](https://insights.sbomify.com/CVE-2024-8507/): File Manager Pro <= 8.3.9 - Cross-Site Request Forgery to Arbitrary File Upload (high 8.8)
- [CVE-2024-1538](https://insights.sbomify.com/CVE-2024-1538/): File Manager <= 7.2.4 - Cross-Site Request Forgery to Local JS File Inclusion (high 8.8)
- [CVE-2023-6846](https://insights.sbomify.com/CVE-2023-6846/): File Manager Pro <= 8.3.4 - Authenticated (Subscriber+) Arbitrary File Upload (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-16363 and fix it if it is affected.

What it is: CVE-2018-16363 is a medium-severity cross-site scripting vulnerability in n/a, published on 7 Sep 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-16363 exists.

Affected product: n/a. 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-2018-16363/ (Markdown: https://insights.sbomify.com/CVE-2018-16363/index.md)
```

## Sources

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

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