CVE-2025-14472

8.1

Drupal · Acquia Content Hub

A Cross-Site Request Forgery (CSRF) vulnerability exists in the Drupal Acquia Content Hub module, potentially allowing unauthorized actions on behalf of a victim user.

Executive summary

A high-severity Cross-Site Request Forgery vulnerability in the Drupal Acquia Content Hub module could allow an attacker to perform unauthorized actions on behalf of authenticated users.

Vulnerability

The module is susceptible to a Cross-Site Request Forgery (CWE-352) attack, which occurs when a malicious site causes a user's browser to perform unwanted actions on a different site where the user is currently authenticated. This vector requires a victim to interact with malicious content while holding an active session.

Business impact

The vulnerability carries a CVSS score of 8.1, indicating a high risk to system integrity and confidentiality. Successful exploitation could lead to unauthorized administrative or data-modifying actions within the Drupal environment, potentially resulting in data loss, configuration changes, or unauthorized content publication. The impact is significant for organizations relying on Acquia Content Hub for content syndication and management.

Remediation

Immediate Action: Update the Acquia Content Hub module to version 3.6.4 or 3.7.3, or the latest available stable release, to apply the necessary CSRF protection.

Proactive Monitoring: Review web server access logs for suspicious requests originating from external domains or unexpected referrers that target Acquia Content Hub endpoints.

Compensating Controls: Ensure that strict SameSite cookie attributes are configured for the Drupal application to mitigate the risk of cross-site request forgery while the update process is being scheduled.

Exploitation status

Public Exploit Available: No (exploit_available: false)

Analyst recommendation

Given the high CVSS score and the nature of CSRF vulnerabilities, organizations should prioritize updating the Acquia Content Hub module during the next maintenance cycle. Failure to patch leaves the Drupal instance exposed to unauthorized state-changing operations that can bypass standard security controls.

More Drupal CVEs

Sources

Originally found and disclosed by Lee Rowlands (larowlan), with Kirti Garg (kirti_garg) (remediation developer), Narendra Shenvi Desai (n4r3n) (remediation developer), Peter Pajor (pajor) (remediation developer), Greg Knaddison (greggles) (coordinator), Juraj Nemec (poker10) (coordinator), per the CVE Program record.