# CVE-2021-40261: Cross-site scripting in n/a

> Multiple Cross-Site Scripting vulnerabilities in CASAP Automated Enrollment System allow attackers to inject malicious scripts via various input parameters.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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:** 8 Nov 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4vx9-wfh3-p3v2

## What is CVE-2021-40261?

CVE-2021-40261 is a medium-severity cross-site scripting vulnerability in n/a, published on 8 Nov 2021. 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

Multiple Cross Site Scripting (XSS) vulnerabilities exist in SourceCodester CASAP Automated Enrollment System 1.0 via the (1) user_username and (2) category parameters in save_class.php, the (3) firstname, (4) class, and (5) status parameters in student_table.php, the (6) category and (7) class_name parameters in add_class1.php, the (8) fname, (9) mname,(10) lname, (11) address, (12) class, (13) gfname, (14) gmname, (15) glname, (16) rship, (17) status, (18) transport, and (19) route parameters in add_student.php, the (20) fname, (21) mname, (22) lname, (23) address, (24) class, (25) fgname, (26) gmname, (27) glname, (28) rship, (29) status, (30) transport, and (31) route parameters in save_stud.php,the (32) status, (33) fname, and (34) lname parameters in add_user.php, the (35) username, (36) firstname, and (37) status parameters in users.php, the (38) fname, (39) lname, and (40) status parameters in save_user.php, and the (41) activity_log, (42) aprjun, (43) class, (44) janmar, (45) Julsep,(46) octdec, (47) Students and (48) users parameters in table_name.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Casap Automated Enrollment System Project Casap Automated Enrollment System.

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

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

## Is CVE-2021-40261 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-26223](https://insights.sbomify.com/CVE-2021-26223/): SQL injection in n/a (critical 9.8)
- [CVE-2021-26226](https://insights.sbomify.com/CVE-2021-26226/): SQL injection in n/a (critical 9.8)
- [CVE-2021-26228](https://insights.sbomify.com/CVE-2021-26228/): SQL injection in n/a (critical 9.8)
- [CVE-2021-26229](https://insights.sbomify.com/CVE-2021-26229/): SQL injection in n/a (critical 9.8)
- [CVE-2021-26201](https://insights.sbomify.com/CVE-2021-26201/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-40261 is a medium-severity cross-site scripting vulnerability in n/a, published on 8 Nov 2021. 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-2021-40261 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-2021-40261/ (Markdown: https://insights.sbomify.com/CVE-2021-40261/index.md)
```

## Sources

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

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