dbcve.org
Ai Seo\/geo AnalyzerDrupal extension · J Vee

CVE-2026-15085

MEDIUM · 5.4 CVSS v3.1 Published 2026-07-10
Fix available
A fix is available. Upgrade to 1.1.3 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable 6 weeks old

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
Improper Neutralization of Input During Web Page Generation ("Cross-site Scripting") vulnerability in Drupal AI SEO/GEO Analyzer allows Stored XSS. This issue affects AI SEO/GEO Analyzer versions: from 0.0.0 to 1.1.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

Stored XSS vulnerability in Drupal AI SEO/GEO Analyzer module allows attackers to inject malicious JavaScript through unsanitized user inputs that get stored and executed when other users view affected pages. This affects versions 0.0.0 through 1.1.3.

MitigationUpgrade to a patched version of the AI SEO/GEO Analyzer module that implements proper input sanitization and output encoding, or apply Drupal's built-in XSS prevention functions to all user-supplied data before rendering.

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\/geo AnalyzerDrupal extension
Affected:< 1.1.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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 AI SEO/GEO Analyzer module is installed
    Run 'drush pm-list' or check the modules directory for the ai_seo_geo_analyzer or similar named module folder in /modules directory
    Affected if The module is present in the Drupal installation
  2. Check installed module version
    Examine the module's .info.yml file or run 'drush pm:info ai_seo_geo_analyzer' to retrieve the version number
    Affected if The version is 1.1.3 or lower (0.0.0 through 1.1.3)
  3. Identify user input fields in the module
    Review form definitions and content processing handlers in the module's source files for fields that accept user-provided SEO/GEO data
    Affected if The module accepts and stores user-supplied input through form fields or content analysis features
  4. Verify output encoding is absent
    Search module source code for use of Drupal XSS filtering functions such as '\Drupal\Component\Utility\Xss::filterAdmin()', 'check_plain()', or Twig's '|escape' filter on user input storage and display paths
    Affected if User input is rendered without applying Drupal's XSS sanitization functions

The environment is affected if the AI SEO/GEO Analyzer module is installed at version 1.1.3 or lower and user-supplied data is processed and displayed without XSS sanitization.

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.1.3 or later
Fixed in 1.1.3
Interim mitigation

Upgrade to a patched version of the AI SEO/GEO Analyzer module that implements proper input sanitization and output encoding, or apply Drupal's built-in XSS prevention functions to all user-supplied data before rendering.

Recommended fix Moderate confidence

1.1.4 or later

  1. Backup your Drupal site database and files before making any changes
  2. Navigate to the Drupal administration panel for module management
  3. Locate the AI SEO/GEO Analyzer module in the module list
  4. Check for available updates - look for version 1.1.4 or newer
  5. If an update is available, download and install the newer version
  6. Verify the update was successful by confirming the module version shows 1.1.4 or higher
  7. Clear Drupal caches after the upgrade via admin/config/development/performance or using drush cr
Caveat Review module release notes for any configuration or feature changes between your current version and the new version before upgrading

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

Fix this in Ai Seo\/geo Analyzer Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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