# CVE-2018-16553: Code injection in n/a

> Remote code execution is possible in Jspxcms after logging in as a web admin due to vulnerable URL routing.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jun 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h5p6-p2x9-xj23

## What is CVE-2018-16553?

CVE-2018-16553 is a high-severity code injection vulnerability in n/a, published on 20 Jun 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

In Jspxcms 9.0.0, a vulnerable URL routing implementation allows remote code execution after logging in as web admin.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Jspxcms Jspxcms.

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

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

## Is CVE-2018-16553 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-20596](https://insights.sbomify.com/CVE-2018-20596/): Jspxcms v9.0.0 allows SSRF. (critical 9.8)
- [CVE-2023-46911](https://insights.sbomify.com/CVE-2023-46911/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2024-1200](https://insights.sbomify.com/CVE-2024-1200/): Jspxcms information disclosure (medium 5.3)
- [CVE-2024-0721](https://insights.sbomify.com/CVE-2024-0721/): Jspxcms Survey Label cross site scripting (low 3.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-16553 is a high-severity code injection vulnerability in n/a, published on 20 Jun 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-16553 in the wild and no public exploit code.

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-16553/ (Markdown: https://insights.sbomify.com/CVE-2018-16553/index.md)
```

## Sources

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

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