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

CVE-2025-58860

HIGH · 7.1 CVSS v3.1 Published 2025-09-05
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 KaizenCoders Enable Latex enable-latex allows Stored XSS.This issue affects Enable Latex: from n/a through <= 1.2.16.

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 Cross-Site Request Forgery (CSRF) vulnerability in the KaizenCoders Enable Latex WordPress plugin allows attackers to craft malicious requests that result in Stored XSS. The plugin fails to properly validate the origin of requests, enabling authenticated administrators to be tricked into submitting requests that inject and persist malicious scripts.

MitigationUpdate to the latest patched version of Enable Latex when available. Until then, implement anti-CSRF nonce validation on all plugin forms and actions, and ensure proper input sanitization and output escaping for all LaTeX 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. Identify if Enable Latex plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Enable Latex' by KaizenCoders, or check the /wp-content/plugins/ directory for the enable-latex folder
    Affected if The plugin is installed and active
  2. Determine the installed plugin version
    In WordPress admin Plugins list, click on the plugin name to view details, or open the main plugin PHP file (enable-latex.php) and look for the Version header comment
    Affected if The version is unknown or unpatched (no patched version was specified in the CVE disclosure)
  3. Inspect plugin forms for CSRF protection
    Examine the plugin PHP files for admin form handlers - check if wp_nonce_field, wp_nonce_url, or check_admin_referer are used on all form submissions and AJAX actions
    Affected if Forms and actions lack nonce validation or origin checks
  4. Check stored LaTeX content for malicious scripts
    Review any custom CSS/JS or LaTeX that may have been saved through the plugin admin interface, and inspect the database wp_options table for any Enable Latex-related entries
    Affected if Unexpected or suspicious script tags are found in stored plugin settings or rendered LaTeX output

A user is affected if the Enable Latex plugin is active and its admin forms lack proper CSRF nonce validation, allowing injection of persistent malicious scripts.

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 Enable Latex when available. Until then, implement anti-CSRF nonce validation on all plugin forms and actions, and ensure proper input sanitization and output escaping for all LaTeX rendering.

Recommended fix Moderate confidence

Upgrade to Enable Latex version 1.2.17 or latest available version

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to Dashboard > Plugins in your WordPress admin panel
  3. 3. Locate the 'Enable Latex' plugin by KaizenCoders
  4. 4. Check the current installed version (should be <= 1.2.16)
  5. 5. If an update is available, click 'Update Now' to upgrade to the latest version
  6. 6. Verify the update completed successfully
  7. 7. Confirm the new version is at least 1.2.17 or higher

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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