# CVE-2023-27037: SQL injection in n/a

> Attackers can execute arbitrary code on QiboCMS servers via SQL injection in the Get_Title function, requiring immediate patching.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Mar 2023
- **Updated:** 26 Feb 2025
- **Also known as:** GHSA-ccfg-9f3p-jm5r

## What is CVE-2023-27037?

CVE-2023-27037 is a high-severity SQL injection vulnerability in n/a, published on 16 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Qibosoft QiboCMS v7 was discovered to contain a remote code execution (RCE) vulnerability via the Get_Title function at label_set_rs.php

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Qibosoft Qibocms.

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

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

## Is CVE-2023-27037 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-18022](https://insights.sbomify.com/CVE-2020-18022/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-27037 is a high-severity SQL injection vulnerability in n/a, published on 16 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-27037 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-2023-27037/ (Markdown: https://insights.sbomify.com/CVE-2023-27037/index.md)
```

## Sources

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

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