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

> An admin can inject XSS payloads via the Job Title field, allowing script execution on the registration page for other users.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 31 Mar 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-w3cp-r2x3-pw86

## What is CVE-2021-29663?

CVE-2021-29663 is a medium-severity cross-site scripting vulnerability in n/a, published on 31 Mar 2021. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

CourseMS (aka Course Registration Management System) 2.1 is affected by cross-site scripting (XSS). When an attacker with access to an Admin account creates a Job Title in the Site area (aka the admin/add_jobs.php name parameter), they can insert an XSS payload. This payload will execute whenever anyone visits the registration page.

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

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

It affects 1 product.


Products: Course Registration Management System Project Course Registration Management System.

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

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

## Is CVE-2021-29663 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-29663 is a medium-severity cross-site scripting vulnerability in n/a, published on 31 Mar 2021. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-29663 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-29663/ (Markdown: https://insights.sbomify.com/CVE-2021-29663/index.md)
```

## Sources

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

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