# CVE-2020-35273: Cross-site request forgery in n/a

> Attackers can exploit CSRF to modify user profiles and gain privileges in the EgavilanMedia User Registration & Login System.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Dec 2020
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-92h4-jh72-6gpm

## What is CVE-2020-35273?

CVE-2020-35273 is a high-severity vulnerability in n/a, published on 21 Dec 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

EgavilanMedia User Registration & Login System with Admin Panel 1.0 is affected by Cross Site Request Forgery (CSRF) to remotely gain privileges in the User Profile panel. An attacker can update any user's account.

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

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

It affects 1 product.


Products: Egavilanmedia User Registration \& Login System With Admin Panel.

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

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

## Is CVE-2020-35273 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-35273 is a high-severity vulnerability in n/a, published on 21 Dec 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-35273 in the wild and no public exploit code.

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

## Sources

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

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