# CVE-2023-52265: Cross-site scripting in n/a

> Attackers can inject malicious scripts into email templates, potentially stealing user sessions or executing code in victim browsers.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **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:** 30 Dec 2023
- **Updated:** 17 Apr 2025
- **Also known as:** GHSA-h9qp-4fch-g5rw

## What is CVE-2023-52265?

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

### Official description

IDURAR (aka idurar-erp-crm) through 2.0.1 allows stored XSS via a PATCH request with a crafted JSON email template in the /api/email/update data.

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

## Which versions are affected by CVE-2023-52265?

It affects 1 product.


Products: Idurarapp Idurar.

## How do I fix CVE-2023-52265?

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

## Is CVE-2023-52265 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-27742](https://insights.sbomify.com/CVE-2023-27742/): SQL injection in n/a (critical 9.8)
- [CVE-2024-47769](https://insights.sbomify.com/CVE-2024-47769/): IDURAR has a Path Traversal (unauthenticated user can read sensitive data) (high 7.5)
- [CVE-2024-25164](https://insights.sbomify.com/CVE-2024-25164/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-52265 and fix it if it is affected.

What it is: CVE-2023-52265 is a medium-severity cross-site scripting vulnerability in n/a, published on 30 Dec 2023. Any signed-in user can exploit it over the network, 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-2023-52265 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-2023-52265/ (Markdown: https://insights.sbomify.com/CVE-2023-52265/index.md)
```

## Sources

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

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