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

> Administrators can inject JavaScript into email templates, leading to arbitrary code execution in user browsers via stored XSS.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Mar 2025
- **Updated:** 19 Mar 2025
- **Also known as:** GHSA-7vrv-rgqg-9p2j

## What is CVE-2025-25363?

CVE-2025-25363 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 Mar 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

An authenticated stored cross-site scripting (XSS) vulnerability in The Plugin People Enterprise Mail Handler for Jira Data Center (JEMH) before v4.1.69-dc allows attackers with Administrator privileges to execute arbitrary Javascript in context of a user's browser via injecting a crafted payload into the HTML field of a template.

Weakness: CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page)

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

It affects 1 product.


Products: Thepluginpeople Enterprise Mail Handler.

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

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

## Is CVE-2025-25363 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-25363 is a medium-severity cross-site scripting vulnerability in n/a, published on 13 Mar 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-25363 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-2025-25363/ (Markdown: https://insights.sbomify.com/CVE-2025-25363/index.md)
```

## Sources

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

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