dbcve.org
Acquia Content HubDrupal extension · Acquia

CVE-2025-14472

HIGH · 8.1 CVSS v3.1 Published 2026-01-28
Fix available
A fix is available. Upgrade to 3.6.4 / 3.7.3 or later.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in Drupal Acquia Content Hub module allows attackers to trick authenticated users into unknowingly executing unwanted actions. The vulnerability affects versions 3.6.x before 3.6.4 and 3.7.x before 3.7.3, potentially allowing unauthorized state-changing requests to be made on behalf of legitimate users.

MitigationUpdate Acquia Content Hub to version 3.6.4 or 3.7.3 or later to receive the security patch. Additionally, ensure proper CSRF token validation is implemented on all state-changing form submissions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Acquia Content HubDrupal extension
Affected:< 3.6.4>= 3.7.0, < 3.7.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Acquia Content Hub module is installed
    In Drupal admin, go to Extend or use drush pm-list --type=module to list installed modules. Confirm 'Acquia Content Hub' or 'acquia_contenthub' module is present.
    Affected if The module is not installed or not enabled - no CSRF risk from this component.
  2. Determine installed module version
    Check the module's .info.yml file or composer.json for the version number. In Drupal admin Extend page, the version may display next to the module name. Alternatively, run 'drush pm-list --type=module --format=json' and look for acquia_contenthub version.
    Affected if Cannot determine version - treat as potentially affected.
  3. Compare version against vulnerable ranges
    If version is 3.6.x, ensure it is 3.6.4 or later. If version is 3.7.x, ensure it is 3.7.3 or later. Versions 3.6.0 through 3.6.3 and 3.7.0 through 3.7.2 are vulnerable.
    Affected if Version is 3.6.0-3.6.3 or 3.7.0-3.7.2 - the environment is affected by this CSRF vulnerability.
  4. Identify exposed state-changing forms
    Review which Content Hub forms and endpoints accept user submissions. Check admin/config/services/contenthub for any forms that modify settings, trigger sync actions, or change content states.
    Affected if No state-changing forms exist or are accessible to authenticated users - exploit surface may be limited, but version still vulnerable.

Environment is affected if Acquia Content Hub module is installed with version 3.6.0-3.6.3 or 3.7.0-3.7.2, as these versions lack proper CSRF token validation on state-changing operations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.6.4 / 3.7.3 or later
Fixed in 3.6.43.7.3
Interim mitigation

Update Acquia Content Hub to version 3.6.4 or 3.7.3 or later to receive the security patch. Additionally, ensure proper CSRF token validation is implemented on all state-changing form submissions.

Recommended fix High confidence

3.6.4 or 3.7.3 (depending on your current branch)

  1. Backup your Drupal site database and files
  2. Update the Acquia Content Hub module to version 3.6.4 (if currently below 3.6.4) or 3.7.3 (if currently between 3.7.0 and 3.7.2)
  3. Run Drupal database updates (drush updatedb or via admin UI)
  4. Clear all Drupal caches (drush cr)
  5. Verify the module is updated by checking /admin/modules or via drush pm:list

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Acquia Content Hub Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14472 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14472 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data