dbcve.org
Ai Seo Link AdvisorDrupal extension · Ai Seo Link Advisor Project

CVE-2025-8675

HIGH · 8.8 CVSS v3.1 Published 2025-08-15
Fix available
A fix is available. Upgrade to 1.0.6 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
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.

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 · high confidence

Server-Side Request Forgery (SSRF) vulnerability in the Drupal AI SEO Link Advisor module allows remote attackers to induce the server to make arbitrary HTTP requests to internal or external resources. This can lead to exposure of internal services, port scanning, or data exfiltration.

MitigationUpdate the AI SEO Link Advisor module to version 1.0.6 or later to obtain the patched code that implements proper URL validation and restricts request destinations.

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
Ai Seo Link AdvisorDrupal extension
Affected:< 1.0.6

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify if Drupal AI SEO Link Advisor module is installed
    Locate the module directory: typically in /modules/contrib/ai_seo_link_advisor or /sites/all/modules/ai_seo_link_advisor. Check for the presence of this directory in your Drupal installation.
    Affected if The ai_seo_link_advisor directory exists in the modules folder
  2. Determine the installed module version
    Check the info file (ai_seo_link_advisor.info.yml) or composer.json in the module directory for the version number. The file usually contains a 'version' or 'core' and 'version' field.
    Affected if The version field shows a version lower than 1.0.6 or no version is specified (indicating an unpatched development release)
  3. Verify if the module is enabled in Drupal
    Run command: drush pm-list --status=enabled | grep -i 'ai seo link advisor' or check the /admin/modules page in the Drupal administration interface.
    Affected if The module shows as enabled or installed in the Drupal system
  4. Confirm the vulnerability trigger is accessible
    The SSRF vulnerability exists in the Link Advisor functionality. Check if the module's configuration allows external URL analysis or link checking features. Inspect the module's routing at /admin/config/ai-seo-link-advisor or similar paths.
    Affected if The module is configured and its link advisor feature is accessible to users

You are affected if the Drupal AI SEO Link Advisor module is installed, enabled, and its version is lower than 1.0.6, as this allows the SSRF vulnerability to be exploited.

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 1.0.6 or later
Fixed in 1.0.6
Interim mitigation

Update the AI SEO Link Advisor module to version 1.0.6 or later to obtain the patched code that implements proper URL validation and restricts request destinations.

Recommended fix High confidence

1.0.6

  1. Backup your Drupal site database and files before proceeding
  2. Download AI SEO Link Advisor version 1.0.6 from drupal.org or the Drupal module repository
  3. Navigate to the Drupal admin panel and go to Extend (or use Drush/Composer)
  4. Deinstall the existing vulnerable version of AI SEO Link Advisor
  5. Install the updated AI SEO Link Advisor version 1.0.6
  6. Run any pending database updates via drush updb or through the admin UI
  7. Clear the Drupal cache to ensure the new module version is fully loaded
  8. Verify the module is now running version 1.0.6 through the Extend page or drush pm:list
Caveat Review module release notes for any configuration or dependency changes before upgrading

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

Fix this in Ai Seo Link Advisor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8675 — 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-8675 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