# CVE-2023-27040: Code injection in n/a

> Attackers can execute arbitrary code remotely via the username parameter in Simple Image Gallery.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 16 Mar 2023
- **Updated:** 26 Feb 2025
- **Also known as:** GHSA-fwvf-42p7-96jh

## What is CVE-2023-27040?

CVE-2023-27040 is a critical code injection vulnerability in n/a, published on 16 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Simple Image Gallery v1.0 was discovered to contain a remote code execution (RCE) vulnerability via the username parameter.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

It affects 1 product.


Products: Simple Image Gallery Web App Project Simple Image Gallery Web App.

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

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

## Is CVE-2023-27040 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-38753](https://insights.sbomify.com/CVE-2021-38753/): File upload in n/a (critical 9.8)
- [CVE-2021-38819](https://insights.sbomify.com/CVE-2021-38819/): SQL injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-27040 is a critical code injection vulnerability in n/a, published on 16 Mar 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-27040 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-27040/ (Markdown: https://insights.sbomify.com/CVE-2023-27040/index.md)
```

## Sources

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

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