# CVE-2023-27180: Information disclosure in n/a

> Attackers can access the backup feature to disclose source code, potentially exposing sensitive application logic and credentials.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Apr 2023
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-v46r-626m-f3pp

## What is CVE-2023-27180?

CVE-2023-27180 is a high-severity vulnerability in n/a, published on 7 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GDidees CMS v3.9.1 was discovered to contain a source code disclosure vulnerability by the backup feature which is accessible via /_admin/backup.php.

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

## Which versions are affected by CVE-2023-27180?

It affects 1 product.


Products: Gdidees Gdidees Cms.

## How do I fix CVE-2023-27180?

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

## Is CVE-2023-27180 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-27180 exists.

## Other vulnerabilities in n/a

- [CVE-2024-46101](https://insights.sbomify.com/CVE-2024-46101/): File upload in n/a (critical 9.8)
- [CVE-2023-27178](https://insights.sbomify.com/CVE-2023-27178/): File upload in n/a (critical 9.8)
- [CVE-2023-27179](https://insights.sbomify.com/CVE-2023-27179/): Path traversal in n/a (high 7.5)
- [CVE-2023-44758](https://insights.sbomify.com/CVE-2023-44758/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-27180 and fix it if it is affected.

What it is: CVE-2023-27180 is a high-severity vulnerability in n/a, published on 7 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-27180 exists.

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-2023-27180/ (Markdown: https://insights.sbomify.com/CVE-2023-27180/index.md)
```

## Sources

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

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