# CVE-2018-7035: Gleez CMS Stored XSS

> Remote attackers can inject JavaScript via HTML content in the editor, leading to Stored XSS when administrators edit the content.

- **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:** 5 Apr 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-m2r2-qc49-gqw4

## What is CVE-2018-7035?

CVE-2018-7035 is a medium-severity cross-site scripting vulnerability in n/a, published on 5 Apr 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

Cross-site scripting (XSS) vulnerability in Gleez CMS 1.2.0 and 2.0 might allow remote attackers (users) to inject JavaScript via HTML content in an editor, which will result in Stored XSS when an Administrator tries to edit the same content, as demonstrated by use of the source editor for HTML mode in an Add Blog action.

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

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

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


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

Products: Gleezcms Gleez Cms.

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

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

## Is CVE-2018-7035 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-27312](https://insights.sbomify.com/CVE-2021-27312/): Gleez Cms Server Side Request Forgery (SSRF) vulnerability (critical 9.4)
- [CVE-2018-15845](https://insights.sbomify.com/CVE-2018-15845/): Gleez CMS CSRF Allows Adding of Administrator Accounts (high 8.8)
- [CVE-2018-16347](https://insights.sbomify.com/CVE-2018-16347/): Gleez CMS Vulnerable to Cross-site Scripting in media/imagecache/resize (medium 6.1)

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- gleez/cms (Packagist): affected all versions; no fix listed
- gleez/cms (Packagist): affected all versions; no fix listed
- gleez/cms (Packagist): affected all versions up to 1.2.0; no fix listed
- gleez/cms (Packagist): affected all versions up to 1.2.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-7035/ (Markdown: https://insights.sbomify.com/CVE-2018-7035/index.md)
```

## Sources

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

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