# CVE-2025-13979: Mini site - Moderately critical - Cross-Site Scripting - SA-CONTRIB-2025-117

> An attacker can inject malicious scripts into the Drupal Mini site module, potentially leading to session hijacking or unauthorized actions.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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:** Not needed
- **Fix available:** Yes
- **Published:** 28 Jan 2026
- **Updated:** 29 Jan 2026
- **Also known as:** DRUPAL-CONTRIB-2025-117, GHSA-mwgm-j9q4-3cm5

## What is CVE-2025-13979?

CVE-2025-13979 is a medium-severity cross-site scripting vulnerability in Drupal Mini site, published on 28 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Privilege Defined With Unsafe Actions vulnerability in Drupal Mini site allows Stored XSS.This issue affects Mini site: from 0.0.0 before 3.0.2.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-267 (Privilege Defined With Unsafe Actions)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/minisite` | Packagist:https://packages.drupal.org/8 | All versions | 3.0.2 |

Products: Salsa.digital Mini Site.

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

Upgrade to a fixed version.

## Is CVE-2025-13979 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13979 is a medium-severity cross-site scripting vulnerability in Drupal Mini site, published on 28 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-13979 in the wild and no public exploit code.

Affected product: Drupal Mini site. 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-13979/ (Markdown: https://insights.sbomify.com/CVE-2025-13979/index.md)
```

## Sources

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

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