# CVE-2020-15182: Cross-site Request Forgery leading to RCE in SOY CMS


- **Severity:** High 8.4 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Sep 2020
- **Updated:** 4 Aug 2024

## What is CVE-2020-15182?

CVE-2020-15182 is a high-severity vulnerability in inunosinsi soycms, published on 17 Sep 2020. 

### Official description

The SOY Inquiry component of SOY CMS is affected by Cross-site Request Forgery (CSRF) and Remote Code Execution (RCE). The vulnerability affects versions 2.0.0.3 and earlier of SOY Inquiry. This allows remote attackers to force the administrator to edit files once the administrator loads a specially crafted webpage. An administrator must be logged in for exploitation to be possible. This issue is fixed in SOY Inquiry version 2.0.0.4 and included in SOY CMS 3.0.2.328.

Weakness: CWE-352 (Cross-Site Request Forgery), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 2 products.


Products: Soy Cms Project Soy Cms, Soy Inquiry Project Soy Inquiry.

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

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

## Is CVE-2020-15182 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-15182 is a high-severity vulnerability in inunosinsi soycms, published on 17 Sep 2020. 
Exploitation: There is no known exploitation of CVE-2020-15182 in the wild and no public exploit code.

Affected product: inunosinsi soycms. 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-15182/ (Markdown: https://insights.sbomify.com/CVE-2020-15182/index.md)
```

## Sources

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

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