CVE-2025-14472VulnerabilityPublished 28 Jan 2026

CVE-2025-14472: Drupal Acquia Content Hub · Cross-Site Request Forgery (CSRF)

Affects Drupal Acquia Content HubSource CVE Database V5

Not known to be exploited · CVSS 8.1 High : upgrade to 3.7.3 or 3.6.4 soon.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

8.1High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.7.3, 3.6.4

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Drupal Acquia Content Hub to 3.7.3 or 3.6.4.

Affected software

Product	Affected	Fixed in
DrupalAcquia Content Hub	Affected <3.6.4 >=3.7.0 <3.7.3	Fixed in 3.7.3 3.6.4

AI-suggested

European organizations should immediately verify their Drupal Acquia Content Hub versions and upgrade to versions 3.6.4 or later, or 3.7.3 or later, where the vulnerability is patched. If upgrading is not immediately possible, implement strict CSRF token validation on all forms and state-changing requests within the Content Hub module. Employ Content Security Policy (CSP) headers to restrict the origins that can interact with the site, reducing the risk of malicious cross-site requests. Enforce secure cookie attributes (HttpOnly, Secure, SameSite=strict) to limit cookie exposure. Conduct thorough audits of user permissions to minimize the number of users with content modification rights, reducing potential attack impact. Monitor web server logs and Drupal audit logs for unusual or unauthorized content changes. Educate users about the risks of interacting with suspicious links while authenticated. Consider deploying web application firewalls (WAFs) with custom rules to detect and block CSRF attack patterns targeting Acquia Content Hub endpoints. Finally, maintain an incident response plan tailored to web application compromises involving content management systems.

Description

CVE-2025-14472 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability affecting Drupal's Acquia Content Hub versions before 3.6.4 and between 3.7.0 and 3.7.3. The vulnerability allows attackers to trick authenticated users into executing unwanted actions on the Content Hub without their consent, potentially leading to unauthorized data modification or leakage. Exploitation requires user interaction but no privileges or authentication from the attacker. The vulnerability impacts confidentiality and integrity but not availability.

Impact

For European organizations, this vulnerability poses a significant risk to the confidentiality and integrity of web content managed via Drupal Acquia Content Hub. Organizations relying on this module for content distribution or synchronization could face unauthorized content modifications, potentially leading to misinformation, reputational damage, or data breaches. Given the network attack vector and lack of required privileges, attackers can target any authenticated user, increasing the attack surface. Public-facing Drupal sites in sectors such as government, finance, healthcare, and media are particularly at risk due to the sensitivity of their content and regulatory requirements like GDPR. Unauthorized content changes could also facilitate phishing or malware distribution campaigns. Although availability is not impacted, the integrity and confidentiality breaches could result in compliance violations and financial losses. The absence of known exploits in the wild provides a window for proactive mitigation, but the high CVSS score underscores the urgency. The interconnected nature of Acquia Content Hub deployments means a successful attack could propagate malicious changes across multiple sites, amplifying the impact.

CWE-352Cross-Site Request Forgery (CSRF) (opens in a new tab)
Compound weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #3OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation
Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
Architecture and Design
Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
REST Security (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V13.2.3 (opens in a new tab)
V4.2.2 (opens in a new tab)
V13.3.2 (opens in a new tab)
Attack patterns
JSON Hijacking (aka JavaScript Hijacking) (opens in a new tab)
Cross-Domain Search Timing (opens in a new tab)
Cross Site Identification (opens in a new tab)
Cross Site Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

drupal.org/sa-contrib-2025-125 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Feb 2026, 08:52 UTC

WeaknessesCWE-352

Technical details

References

Community reviews

Related threats