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

> Attackers can inject persistent XSS via unrecognized editor tags to compromise higher-privilege user accounts in Bludit CMS.

- **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:** 6 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-w3pq-253h-3gfp

## What is CVE-2017-16636?

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

### Official description

In Bludit v1.5.2 and v2.0.1, an XSS vulnerability is located in the new page, new category, and edit post function body message context. Remote attackers are able to bypass the basic editor validation to trigger cross site scripting. The XSS is persistent and the request method to inject via editor is GET. To save the editor context, the followup POST method request must be processed to perform the attack via the application side. The basic validation of the editor does not allow injecting script codes and blocks the context. Attackers can inject the code by using an editor tag that is not recognized by the basic validation. Thus allows a restricted user account to inject malicious script code to perform a persistent attack against higher privilege web-application user accounts.

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

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

It affects 1 product.


Products: Bludit Bludit.

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

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

## Is CVE-2017-16636 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-18879](https://insights.sbomify.com/CVE-2020-18879/): File upload in n/a (critical 9.8)
- [CVE-2020-20495](https://insights.sbomify.com/CVE-2020-20495/): Path traversal in n/a (critical 9.1)
- [CVE-2020-18190](https://insights.sbomify.com/CVE-2020-18190/): Path traversal in n/a (critical 9.1)
- [CVE-2024-24550](https://insights.sbomify.com/CVE-2024-24550/): Bludit - Remote Code Execution (RCE) through File API (high 8.9)
- [CVE-2024-24551](https://insights.sbomify.com/CVE-2024-24551/): Bludit - Remote Code Execution (RCE) through Image API (high 8.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-16636 is a medium-severity cross-site scripting vulnerability in n/a, published on 6 Nov 2017. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-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-2017-16636/ (Markdown: https://insights.sbomify.com/CVE-2017-16636/index.md)
```

## Sources

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

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