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

> Attackers can inject malicious HTML into Nucleus CMS via the index.php body parameter, potentially executing scripts or stealing data.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-6w76-xxgp-fhm5

## What is CVE-2018-16636?

CVE-2018-16636 is a medium-severity cross-site scripting vulnerability in n/a, published on 10 Dec 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Nucleus CMS 3.70 allows HTML Injection via the index.php body parameter.

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

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

It affects 1 product.


Products: Nucleuscms Nucleus Cms.

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

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

## Is CVE-2018-16636 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-37770](https://insights.sbomify.com/CVE-2021-37770/): File upload in n/a (high 7.2)
- [CVE-2011-3760](https://insights.sbomify.com/CVE-2011-3760/): Information disclosure in n/a (medium 5.0)
- [CVE-2015-5454](https://insights.sbomify.com/CVE-2015-5454/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-16636 is a medium-severity cross-site scripting vulnerability in n/a, published on 10 Dec 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-16636 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-16636/ (Markdown: https://insights.sbomify.com/CVE-2018-16636/index.md)
```

## Sources

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

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