dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-31385

HIGH · 7.1 CVSS v3.1 Published 2025-04-09
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
Cross-Site Request Forgery (CSRF) vulnerability in intelcaprep Site Table of Contents site-table-of-contents allows Stored XSS.This issue affects Site Table of Contents: from n/a through <= 0.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

A CSRF vulnerability in the Site Table of Contents plugin allows attackers to inject malicious JavaScript through stored XSS by tricking authenticated administrators into triggering crafted requests. The flaw exists because the plugin lacks anti-CSRF token validation on form submissions that modify content, enabling attackers to execute arbitrary scripts in the browsers of users viewing the affected table of contents.

MitigationImplement anti-CSRF tokens on all state-changing form submissions and update to the latest patched version once available. Validate the origin and referer headers as additional defense-in-depth.

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. Verify Site Table of Contents plugin is installed
    Navigate to the plugins administration panel and locate the Site Table of Contents plugin. Note its activation status and version number if displayed.
    Affected if the plugin is installed and active, making the CSRF attack surface available
  2. Identify the installed plugin version
    Access the plugin files via file manager or FTP. Locate the main plugin file (often named plugin-name.php) and read the version header comment or version constant defined at the top of the file.
    Affected if any version is running, as no fixed version was specified in the advisory
  3. Inspect table of contents entries for XSS payloads
    Access the plugin settings page where the table of contents is configured. Review all TOC entries, headings, or anchor labels for suspicious content such as <script> tags, javascript: URIs, event handlers like onload/onerror, or encoded variants.
    Affected if any TOC entry contains JavaScript code, HTML tags, or unusual characters that could represent injected XSS payloads
  4. Review admin audit logs for form submission anomalies
    Check server access logs, admin action logs, or security plugins for POST requests to the plugin admin pages that lack anti-CSRF tokens or contain unexpected parameter values indicating automated abuse.
    Affected if multiple form submissions from different IP addresses or sessions targeting the plugin settings are observed without corresponding admin actions
  5. Examine rendered page source for injected scripts
    View the source code of pages containing the table of contents. Search for any script tags, eval() calls, or inline event handlers within the TOC container that were not intentionally added by the administrator.
    Affected if the rendered TOC output contains unexpected JavaScript code that was not authored by the site administrator

A user is affected if the Site Table of Contents plugin is installed and active, and either the plugin lacks anti-CSRF protection or the table of contents entries contain malicious scripts injected via CSRF.

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

Implement anti-CSRF tokens on all state-changing form submissions and update to the latest patched version once available. Validate the origin and referer headers as additional defense-in-depth.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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