# CVE-2025-63713: Cross-site scripting in n/a

> Remote attackers can inject arbitrary scripts via unsanitized test titles and items in MatchMaster, potentially leading to session hijacking or malicious actions.

- **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:** 7 Nov 2025
- **Updated:** 12 Nov 2025
- **Also known as:** GHSA-ggfg-472r-q46h

## What is CVE-2025-63713?

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

Cross-Site Scripting (XSS) vulnerability in SourceCodester "MatchMaster" 1.0 allows remote attackers to inject arbitrary web script or HTML via crafted input in the custom test creation feature. The vulnerability exists because the application fails to properly sanitize user-supplied input in test titles and matching pair items before rendering them in the DOM during test execution.

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

## Which versions are affected by CVE-2025-63713?

It affects 1 product.


Products: Remyandrade Matching Type Test.

## How do I fix CVE-2025-63713?

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

## Is CVE-2025-63713 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63713 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-63713 and fix it if it is affected.

What it is: CVE-2025-63713 is a medium-severity cross-site scripting vulnerability in n/a, published on 7 Nov 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63713 exists.

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-2025-63713/ (Markdown: https://insights.sbomify.com/CVE-2025-63713/index.md)
```

## Sources

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

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