CVE-2018-20463 An issue was discovered in the JSmol2WP plugin 1.07 for WordPress.
High 7.5
Published
Updated
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)
- Exploited in the wild
- Not known
- Fix
- None listed
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
Which versions are affected by CVE-2018-20463?
It affects 1 product.
Products include 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: 1 Nuclei template and 1 proofs of concept on GitHub.
Other vulnerabilities in n/a
Sources
Also known as GHSA-qr25-w2r2-h5v4.