# CVE-2020-36539: Lógico y Creativo sql injection

> Remote attackers can exploit SQL injection in the id parameter to read or modify database contents in Lógico y Creativo.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 3 Jun 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-27c3-vpxp-mmff

## What is CVE-2020-36539?

CVE-2020-36539 is a medium-severity SQL injection vulnerability in unspecified Lógico y Creativo, published on 3 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in Lógico y Creativo 1.0 and classified as critical. This issue affects some unknown processing. The manipulation of the argument id leads to sql injection. The attack may be initiated remotely.

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

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

It affects 1 product.


Products: Logicoycreativo Logico Y Creativo.

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

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

## Is CVE-2020-36539 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-36539 is a medium-severity SQL injection vulnerability in unspecified Lógico y Creativo, published on 3 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-36539 in the wild and no public exploit code.

Affected product: unspecified Lógico y Creativo. 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-2020-36539/ (Markdown: https://insights.sbomify.com/CVE-2020-36539/index.md)
```

## Sources

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

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