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

CVE-2025-68836

HIGH · 7.1 CVSS v3.1 Published 2026-03-19
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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Markbeljaars Table of Contents Creator allows Reflected XSS.This issue affects Table of Contents Creator: from n/a through 1.6.4.1.

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

Reflected XSS vulnerability in the Table of Contents Creator WordPress plugin allows attackers to inject malicious JavaScript code via unsanitized user input that gets reflected in the web page without proper output encoding.

MitigationUpdate to the latest patched version of Table of Contents Creator; if unavailable, disable the plugin until a fix is released. Apply output encoding/sanitization to all user-supplied input before rendering.

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 the plugin installation directory
    Navigate to the WordPress wp-content/plugins/ folder and look for a directory named 'table-of-contents-creator', 'toc-creator', or similar variation containing 'toc' or 'table of contents' in the name
    Affected if The plugin directory exists on the server
  2. Read the installed plugin version
    Open the main PHP file in the plugin directory (usually the PHP file with the same name as the folder or a readme.txt file) and locate the 'Version:' header field
    Affected if A version number is found - compare it to the patched version once available
  3. Verify the plugin is active
    In the WordPress admin dashboard, go to Plugins > Installed Plugins and check if Table of Contents Creator shows as 'Active'
    Affected if The plugin is enabled and running on the WordPress site
  4. Identify user input points
    Access the plugin settings page (usually under Settings or the plugin's own menu) and identify any fields that accept user-supplied text which could be reflected in the page output
    Affected if The plugin has settings or input fields where unsanitized user data could be rendered on the frontend
  5. Test for reflected XSS in plugin URLs
    In a non-production environment, access the plugin admin pages and inspect the URL parameters (query strings) for any values that get echoed back in the HTML response without encoding, such as in error messages or confirmation text
    Affected if URL parameters are reflected in the page output without proper encoding

If the Table of Contents Creator plugin is installed, active, and handles any user-supplied input that gets reflected in web pages, the environment may be vulnerable to CVE-2025-68836 until the patched version is confirmed and applied.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest patched version of Table of Contents Creator; if unavailable, disable the plugin until a fix is released. Apply output encoding/sanitization to all user-supplied input before rendering.

Recommended fix Moderate confidence

Table of Contents Creator version 1.6.5 or later

  1. 1. Back up your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Locate the 'Table of Contents Creator' plugin.
  4. 4. Check the current version number to confirm it is 1.6.4.1 or earlier.
  5. 5. Update the plugin to the latest available version (version 1.6.5 or higher, which contains the security fix for CVE-2025-68836).
  6. 6. Verify the update completed successfully.
  7. 7. Test the plugin functionality to ensure the update did not break existing features.
  8. 8. Clear any caching mechanisms if your site uses them.
Caveat Review plugin settings after upgrade as minor configuration changes may occur between versions

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

Have this fixed 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 help mitigating

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-2025-68836 — 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-68836 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