# CVE-2020-26625: Gila CMS SQL Injection vulnerability

> Remote attackers can execute arbitrary SQL commands via the user_id parameter in Gila CMS, potentially compromising database integrity and confidentiality.

- **Severity:** Low 3.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jan 2024
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-3pfj-g4wr-qj3j

## What is CVE-2020-26625?

CVE-2020-26625 is a low-severity SQL injection vulnerability in n/a, published on 2 Jan 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A SQL injection vulnerability was discovered in Gila CMS 1.15.4 and earlier which allows a remote attacker to execute arbitrary web scripts via the 'user_id' parameter after the login portal.

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

## Which versions are affected by CVE-2020-26625?

2 open source packages ship an affected version, including gilacms/gila. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gilacms/gila` | Packagist | All versions to 1.15.4 | None |
| `gilacms/gila` | Packagist | All versions to 1.15.4 | None |

Products: Gilacms Gila Cms.

## How do I fix CVE-2020-26625?

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

## Is CVE-2020-26625 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-17536](https://insights.sbomify.com/CVE-2019-17536/): File upload in n/a (critical 9.9)
- [CVE-2019-17535](https://insights.sbomify.com/CVE-2019-17535/): Cross-site scripting in n/a (critical 9.3)
- [CVE-2020-5514](https://insights.sbomify.com/CVE-2020-5514/): File upload in n/a (critical 9.1)
- [CVE-2020-20726](https://insights.sbomify.com/CVE-2020-20726/): GilaCMS Cross Site Request Forgery vulnerability (high 8.8)
- [CVE-2020-20693](https://insights.sbomify.com/CVE-2020-20693/): Cross-Site Request Forgery in GilaCMS (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-26625 and fix it if it is affected.

What it is: CVE-2020-26625 is a low-severity SQL injection vulnerability in n/a, published on 2 Jan 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-26625 exists.

Affected packages and fixed versions:
- gilacms/gila (Packagist): affected all versions up to 1.15.4; no fix listed
- gilacms/gila (Packagist): affected all versions up to 1.15.4; no fix listed

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

## Sources

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

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