CVE-2025-8675VulnerabilityPublished 15 Aug 2025

CVE-2025-8675: Drupal AI SEO Link Advisor · Server-Side Request Forgery (SSRF)

Affects Drupal AI SEO Link AdvisorSource CVE Database V5

Not known to be exploited · CVSS 4.7 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.7Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: None
Integrity: Low
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: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 15 Aug 2025
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-25.

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

Affected software

Product	Affected	Fixed in
Drupal AI SEO Link Advisor	Affected =0.0.0	Fixed in–

AI-suggested

European organizations should immediately inventory their Drupal installations to identify the presence of the AI SEO Link Advisor module and its version. Until an official patch is released, organizations should consider disabling or uninstalling the module to eliminate the attack surface. If disabling is not feasible, implement strict input validation and URL whitelisting on any user-controllable parameters that influence outbound requests. Network-level mitigations include restricting the Drupal server's outbound HTTP requests via firewall rules or proxy configurations to prevent access to internal IP ranges, metadata services, and sensitive endpoints. Employ web application firewalls (WAFs) with custom rules to detect and block suspicious SSRF patterns. Additionally, educate users about phishing and social engineering risks to reduce the likelihood of triggering the vulnerability. Monitor logs for unusual outbound requests from Drupal servers and anomalous internal network activity. Once a vendor patch or update is available, prioritize its deployment and verify the fix through testing. Finally, maintain up-to-date threat intelligence feeds to detect any emerging exploit attempts targeting this vulnerability.

Description

Server-Side Request Forgery (SSRF) vulnerability in Drupal AI SEO Link Advisor allows Server Side Request Forgery.This issue affects AI SEO Link Advisor: from 0.0.0 before 1.0.6.

Impact

For European organizations using Drupal with the AI SEO Link Advisor module, this SSRF vulnerability poses a moderate risk. Attackers could leverage this flaw to perform internal network scanning or access internal services that are otherwise protected by firewalls or network segmentation. This can lead to further exploitation, such as accessing internal APIs, metadata services in cloud environments, or other sensitive infrastructure components. While direct data exfiltration is not indicated, the integrity impact suggests attackers might manipulate or influence internal requests, potentially causing unauthorized actions or data corruption. Given the widespread use of Drupal in Europe, especially among government, education, and enterprise sectors, the vulnerability could be exploited to gain footholds or pivot within internal networks. The requirement for user interaction (UI:R) implies that some form of social engineering or user-triggered action is needed, which may limit automated exploitation but does not eliminate risk, especially in phishing-prone environments. The medium severity rating aligns with a moderate but non-trivial threat level, warranting timely attention to prevent escalation or chaining with other vulnerabilities.

CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 15 Aug 2025, 17:03 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats