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

> Privileged users can inject persistent malicious scripts via project titles in Weblication CMS, potentially compromising session credentials or manipulating output.

- **Severity:** Medium 4.8 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7g75-9v7p-fmqc

## What is CVE-2018-13002?

CVE-2018-13002 is a medium-severity cross-site scripting vulnerability in n/a, published on 29 Jun 2018. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

An XSS issue was discovered in Inhaltsprojekte in Weblication CMS Core & Grid v12.6.24. The vulnerability is located in the `wFilemanager.php` and `index.php` files of the `/grid5/scripts/` modules. The injection point is located in the Project `Title` and the execution point occurs in the `Inhaltsprojekte` output listing section. Remote attackers with privileged user accounts are able to inject their own malicious script code with a persistent attack vector to compromise user session credentials or to manipulate the affected web-application module output context. The request method to inject is POST.

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

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

It affects 1 product.


Products: Weblication Cms Core \& Grid.

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

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

## Is CVE-2018-13002 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-13002 is a medium-severity cross-site scripting vulnerability in n/a, published on 29 Jun 2018. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-13002 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-13002/ (Markdown: https://insights.sbomify.com/CVE-2018-13002/index.md)
```

## Sources

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

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