# CVE-2025-65271: Code injection in n/a

> Low-privilege users can execute arbitrary template code in admin sessions via client-side template injection, leading to privilege escalation.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Dec 2025
- **Updated:** 11 Dec 2025
- **Also known as:** GHSA-8w85-pvh2-gq59

## What is CVE-2025-65271?

CVE-2025-65271 is a high-severity code injection vulnerability in n/a, published on 8 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Client-side template injection (CSTI) in Azuriom CMS admin dashboard allows a low-privilege user to execute arbitrary template code in the context of an administrator's session. This can occur via plugins or dashboard components that render untrusted user input, potentially enabling privilege escalation to an administrative account. Fixed in Azuriom 1.2.7.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Azuriom Azuriom.

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

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

## Is CVE-2025-65271 being exploited?

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

Public exploit code:

- PoC for CVE-2025-65271 | Found by me (github_poc): https://github.com/1337Skid/CVE-2025-65271

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65271 is a high-severity code injection vulnerability in n/a, published on 8 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65271 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-65271/ (Markdown: https://insights.sbomify.com/CVE-2025-65271/index.md)
```

## Sources

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

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