# CVE-2018-20463: An issue was discovered in the JSmol2WP plugin 1.07 for WordPress.


- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qr25-w2r2-h5v4

## What is CVE-2018-20463?

CVE-2018-20463 is a high-severity vulnerability in n/a, published on 25 Dec 2018. 

### Official description

An issue was discovered in the JSmol2WP plugin 1.07 for WordPress. There is an arbitrary file read vulnerability via ../ directory traversal in query=php://filter/resource= in the jsmol.php query string. This can also be used for SSRF.

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

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

It affects 1 product.


Products: Jsmol2wp Project Jsmol2wp.

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

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

## Is CVE-2018-20463 being exploited?

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

Public exploit code:

- WordPress JSmol2WP Plugin 1.07版本中存在安全漏洞。攻击者可利用该漏洞读取任意文件。 (github_poc): https://github.com/Henry4E36/CVE-2018-20463
- WordPress JSmol2WP <=1.07 - Local File Inclusion (nuclei): http/cves/2018/CVE-2018-20463.yaml

## Other vulnerabilities in n/a

- [CVE-2018-20462](https://insights.sbomify.com/CVE-2018-20462/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-20463 is a high-severity vulnerability in n/a, published on 25 Dec 2018. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-20463 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-20463/ (Markdown: https://insights.sbomify.com/CVE-2018-20463/index.md)
```

## Sources

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

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