dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2025-68840

HIGH · 7.1 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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
Unauthenticated Cross Site Scripting (XSS) in iRobots.txt SEO <= 1.1.2 versions.

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

Unauthenticated Cross Site Scripting (XSS) vulnerability in the iRobots.txt SEO WordPress plugin versions 1.1.2 and below allows attackers to inject malicious scripts without authentication.

MitigationUpdate iRobots.txt SEO plugin to version greater than 1.1.2; if immediate update is not possible, consider disabling the plugin or deploying a WAF rule to block XSS attack patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

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

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. Locate iRobots.txt SEO plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'irobots-txt-seo' or similar, or query the WordPress database wp_options table for option_name containing 'active_plugins' to see if the plugin is loaded.
    Affected if The plugin folder exists in wp-content/plugins/ or the plugin is listed in active site-wide or network-active plugins.
  2. Identify installed plugin version
    Open the main plugin PHP file (usually index.php or irobots-txt-seo.php) in the plugin directory and locate the Version header in the plugin comment block, or check the readme.txt file for the 'Stable tag' entry.
    Affected if The version displayed is 1.1.2 or any version lower than 1.1.2.
  3. Verify plugin is active and accessible
    In the WordPress admin dashboard, navigate to Plugins > Installed Plugins and confirm iRobots.txt SEO shows as 'Active', or use wp-cli: wp plugin list --status=active --field=name | grep -i irobots.
    Affected if The plugin is active and publicly accessible (the XSS is unauthenticated, meaning no login is required to trigger it).

If iRobots.txt SEO plugin version 1.1.2 or lower is installed and active, the environment is vulnerable to unauthenticated XSS attacks.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update iRobots.txt SEO plugin to version greater than 1.1.2; if immediate update is not possible, consider disabling the plugin or deploying a WAF rule to block XSS attack patterns.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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