# CVE-2018-1999021: Gleez Cms Cross-site Scripting in Profile Page

> An attacker can inject arbitrary web script or HTML via the profile page editor, potentially executing code in the victim's browser.

- **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:** 23 Jul 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-q9g7-pff4-548r

## What is CVE-2018-1999021?

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

### Official description

Gleezcms Gleez Cms version 1.3.0 contains a Cross Site Scripting (XSS) vulnerability in Profile page that can result in Inject arbitrary web script or HTML via the profile page editor. This attack appear to be exploitable via The victim must navigate to the attacker's profile page.

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

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

2 open source packages ship an affected version, including gleez/cms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gleez/cms` | Packagist | All versions to 1.3.0 | None |
| `gleez/cms` | Packagist | All versions to 1.3.0 | None |

Products: Gleeztech Gleezcms.

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

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

## Is CVE-2018-1999021 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-16704](https://insights.sbomify.com/CVE-2018-16704/): Gleez CMS Vulnerability Allows Forced Browsing to Profile Page of Other Users (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-1999021 is a medium-severity cross-site scripting vulnerability in n/a, published on 23 Jul 2018. 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-2018-1999021 in the wild and no public exploit code.

Affected packages and fixed versions:
- gleez/cms (Packagist): affected all versions up to 1.3.0; no fix listed
- gleez/cms (Packagist): affected all versions up to 1.3.0; no fix listed

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

## Sources

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

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