# CVE-2025-14472: Acquia Content Hub - Moderately critical - Cross-Site Request Forgery - SA-CONTRIB-2025-125

> Attackers can trick authenticated users into performing unintended actions in the Acquia Content Hub module for Drupal.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **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:** Yes
- **Published:** 28 Jan 2026
- **Updated:** 29 Jan 2026
- **Also known as:** DRUPAL-CONTRIB-2025-125, GHSA-vrpj-mcpc-4663

## What is CVE-2025-14472?

CVE-2025-14472 is a high-severity vulnerability in Drupal Acquia Content Hub, published on 28 Jan 2026. 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

Cross-Site Request Forgery (CSRF) vulnerability in Drupal Acquia Content Hub allows Cross Site Request Forgery.This issue affects Acquia Content Hub: from 0.0.0 before 3.6.4, from 3.7.0 before 3.7.3.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/acquia_contenthub` | Packagist:https://packages.drupal.org/8 | All versions | 3.6.4, 3.7.3 |

Products: Acquia Acquia Content Hub.

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

Upgrade to a fixed version.

## Is CVE-2025-14472 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14472 is a high-severity vulnerability in Drupal Acquia Content Hub, published on 28 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-14472 in the wild and no public exploit code.

Affected product: Drupal Acquia Content Hub. 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-14472/ (Markdown: https://insights.sbomify.com/CVE-2025-14472/index.md)
```

## Sources

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

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