# CVE-2020-36633: moodle-block_sitenews block_sitenews.php get_content cross-site request forgery

> A cross-site request forgery vulnerability in the Moodle sitenews block allows attackers to perform unauthorized actions on behalf of authenticated users.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Dec 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-gqxf-4j76-pqc9

## What is CVE-2020-36633?

CVE-2020-36633 is a medium-severity vulnerability in moodle-block_sitenews, published on 27 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability was found in moodle-block_sitenews 1.0. It has been classified as problematic. This affects the function get_content of the file block_sitenews.php. The manipulation leads to cross-site request forgery. It is possible to initiate the attack remotely. Upgrading to version 1.1 is able to address this issue. The name of the patch is cd18d8b1afe464ae6626832496f4e070bac4c58f. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-216879.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Moodle-Block Sitenews Project Moodle-Block Sitenews.

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

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

## Is CVE-2020-36633 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-36633 is a medium-severity vulnerability in moodle-block_sitenews, published on 27 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-36633 in the wild and no public exploit code.

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

## Sources

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

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