# CVE-2019-11617: Cross-site request forgery in n/a

> A remote attacker can modify Google Analytics code via CSRF in doorGets, requiring user interaction to exploit.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 30 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4jr3-vm5j-595f

## What is CVE-2019-11617?

CVE-2019-11617 is a high-severity vulnerability in n/a, published on 30 Apr 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

doorGets 7.0 has a CSRF vulnerability in /doorgets/app/requests/user/configurationRequest.php. A remote attacker can exploit this vulnerability for "Google Analytics code" modification.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2019-11617?

It affects 1 product.


Products: Doorgets Doorgets Cms.

## How do I fix CVE-2019-11617?

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

## Is CVE-2019-11617 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-11616](https://insights.sbomify.com/CVE-2019-11616/): Information disclosure in n/a (critical 9.8)
- [CVE-2019-11618](https://insights.sbomify.com/CVE-2019-11618/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2019-11615](https://insights.sbomify.com/CVE-2019-11615/): File upload in n/a (high 8.8)
- [CVE-2019-11608](https://insights.sbomify.com/CVE-2019-11608/): Path traversal in n/a (high 8.2)
- [CVE-2019-11609](https://insights.sbomify.com/CVE-2019-11609/): Path traversal in n/a (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-11617 and fix it if it is affected.

What it is: CVE-2019-11617 is a high-severity vulnerability in n/a, published on 30 Apr 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-2019-11617 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-2019-11617/ (Markdown: https://insights.sbomify.com/CVE-2019-11617/index.md)
```

## Sources

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

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