# CVE-2018-20567: Security feature bypass in n/a

> Attackers can bypass installation locks to reinstall DouPHP if the lock file is unreadable, potentially compromising the site integrity.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Dec 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-7ghg-23h8-fj3m

## What is CVE-2018-20567?

CVE-2018-20567 is a medium-severity vulnerability in n/a, published on 28 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in DouCo DouPHP 1.5 20181221. \install\index.php allows a reload of the product in opportunistic circumstances in which install.lock cannot be read.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 1 product.


Products: Douco Douphp.

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

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

## Is CVE-2018-20567 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-12564](https://insights.sbomify.com/CVE-2019-12564/): Information disclosure in n/a (critical 9.8)
- [CVE-2018-20419](https://insights.sbomify.com/CVE-2018-20419/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2022-24131](https://insights.sbomify.com/CVE-2022-24131/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2021-3370](https://insights.sbomify.com/CVE-2021-3370/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2022-46438](https://insights.sbomify.com/CVE-2022-46438/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-20567 is a medium-severity vulnerability in n/a, published on 28 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-20567 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-20567/ (Markdown: https://insights.sbomify.com/CVE-2018-20567/index.md)
```

## Sources

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

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