# CVE-2025-27102: Agate vulnerable to HTML injection in user signup - Administrator phishing risk

> Attackers can inject HTML into user names, leading to phishing attacks against administrators via rendered emails in Agate authentication server.

- **Severity:** Medium 5.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N/E:P`)
- **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:** 17 Mar 2025
- **Updated:** 17 Mar 2025
- **Also known as:** GHSA-v3wj-7vj5-xj5v

## What is CVE-2025-27102?

CVE-2025-27102 is a medium-severity cross-site scripting vulnerability in obiba agate, published on 17 Mar 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

Agate is central authentication server software for OBiBa epidemiology applications. Prior to version 3.3.0, when registering for an Agate account, arbitrary HTML code can be injected into a user's first and last name. This HTML is then rendered in the email sent to administrative users. The Agate service account sends this email and appears trustworthy, making this a significant risk for phishing attacks. Administrative users are impacted, as they can be targeted by unauthenticated users. Version 3.3.0 fixes the issue.

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

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


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

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

## Is CVE-2025-27102 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-27102 is a medium-severity cross-site scripting vulnerability in obiba agate, published on 17 Mar 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-27102 exists.

Affected product: obiba agate. 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-27102/ (Markdown: https://insights.sbomify.com/CVE-2025-27102/index.md)
```

## Sources

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

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