# CVE-2021-27312: Gleez Cms Server Side Request Forgery (SSRF) vulnerability

> Remote attackers can exploit SSRF in Gleez CMS to execute arbitrary code and access sensitive information.

- **Severity:** Critical 9.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 3 Apr 2024
- **Updated:** 28 Aug 2024
- **Also known as:** GHSA-7mxg-r76p-363g

## What is CVE-2021-27312?

CVE-2021-27312 is a critical server-side request forgery vulnerability in n/a, published on 3 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Server Side Request Forgery (SSRF) vulnerability in Gleez Cms 1.2.0, allows remote attackers to execute arbitrary code and obtain sensitive information via modules/gleez/classes/request.php.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2021-27312?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gleez/cms` | Packagist | All versions to 1.2.0 | None |
| `gleez/cms` | Packagist | All versions to 1.2.0 | None |

Products: Gleezcms Gleez Cms.

## How do I fix CVE-2021-27312?

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

## Is CVE-2021-27312 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-15845](https://insights.sbomify.com/CVE-2018-15845/): Gleez CMS CSRF Allows Adding of Administrator Accounts (high 8.8)
- [CVE-2018-16347](https://insights.sbomify.com/CVE-2018-16347/): Gleez CMS Vulnerable to Cross-site Scripting in media/imagecache/resize (medium 6.1)
- [CVE-2018-7035](https://insights.sbomify.com/CVE-2018-7035/): Gleez CMS Stored XSS (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-27312 and fix it if it is affected.

What it is: CVE-2021-27312 is a critical server-side request forgery vulnerability in n/a, published on 3 Apr 2024. 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-2021-27312 exists.

Affected packages and fixed versions:
- gleez/cms (Packagist): affected all versions up to 1.2.0; no fix listed
- gleez/cms (Packagist): affected all versions up to 1.2.0; 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-2021-27312/ (Markdown: https://insights.sbomify.com/CVE-2021-27312/index.md)
```

## Sources

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

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