# CVE-2025-10876: XSS in Talent Software's e-Bap

> Cross-site scripting vulnerability in Talent Software e-BAP Automation allows attackers to inject malicious scripts, potentially leading to session hijacking or data theft.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Dec 2025
- **Updated:** 5 Jun 2026
- **Also known as:** GHSA-qmrc-xc5v-v23c

## What is CVE-2025-10876?

CVE-2025-10876 is a medium-severity cross-site scripting vulnerability in Talent Software e-BAP Automation, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Talent Software e-BAP Automation allows Cross-Site Scripting (XSS).

This issue affects e-BAP Automation: from 1.8.96 before v.41815.

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

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


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

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

## Is CVE-2025-10876 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10876 is a medium-severity cross-site scripting vulnerability in Talent Software e-BAP Automation, published on 9 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-10876 in the wild and no public exploit code.

Affected product: Talent Software e-BAP Automation. 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-10876/ (Markdown: https://insights.sbomify.com/CVE-2025-10876/index.md)
```

## Sources

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

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