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

> Remote attackers can inject arbitrary web script via the HTTP Referer header in the Fabrik component for Joomla.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h88c-6cg3-vvc2

## What is CVE-2018-10727?

CVE-2018-10727 is a medium-severity cross-site scripting vulnerability in n/a, published on 29 Oct 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Reflected Cross-Site Scripting (XSS) vulnerability in the fabrik_referrer hidden field in the Fabrikar Fabrik component through v3.8.1 for Joomla! allows remote attackers to inject arbitrary web script via the HTTP Referer header.

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

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

It affects 1 product.


Products: Fabrikar Fabrik.

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

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

## Is CVE-2018-10727 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-1981](https://insights.sbomify.com/CVE-2010-1981/): Path traversal in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-10727 is a medium-severity cross-site scripting vulnerability in n/a, published on 29 Oct 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-10727 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-10727/ (Markdown: https://insights.sbomify.com/CVE-2018-10727/index.md)
```

## Sources

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

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