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

CVE-2024-53765

HIGH · 7.1 CVSS v3.1 Published 2024-12-02
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 Think201 Mins To Read mins-to-read allows Stored XSS.This issue affects Mins To Read: from n/a through <= 1.2.2.

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 Mins To Read WordPress plugin (versions up to 1.2.2) allows authenticated users to be tricked into submitting malicious requests that result in stored XSS. The lack of proper CSRF token validation on plugin forms enables attackers to inject persistent malicious scripts that execute when other users view the affected content.

MitigationImplement anti-CSRF tokens (nonces) on all state-changing operations and ensure all user inputs are properly sanitized before storage and output.

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 Mins To Read plugin is installed
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, and search for 'Mins To Read' or check the plugin files directly in wp-content/plugins/ directory
    Affected if The plugin appears in the installed plugins list
  2. Check installed plugin version
    In WordPress admin, click on the plugin from the Installed Plugins list to view its details, or read the main plugin PHP file header for the Version field
    Affected if Version is 1.2.2 or lower (any version up to and including 1.2.2)
  3. Inspect plugin forms for CSRF protection
    Examine plugin PHP source code for nonce fields (wp_nonce_field, wp_nonce_url) in form definitions, particularly in admin settings pages or any frontend submission forms
    Affected if Forms lack nonce verification or token validation on state-changing operations
  4. Check input sanitization on stored data
    Review plugin code for usage of sanitization functions (esc_html, esc_attr, sanitize_text_field) when saving and outputting plugin-generated content
    Affected if User-supplied data is stored or displayed without proper sanitization, allowing script injection

You are affected if the Mins To Read plugin is installed at version 1.2.2 or below and its forms lack CSRF token validation combined with inadequate input 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens (nonces) on all state-changing operations and ensure all user inputs are properly sanitized before storage and output.

Recommended fix Moderate confidence

Mins To Read plugin version > 1.2.2 (contact vendor or check WordPress plugin repository for latest stable release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the "Mins To Read" plugin by Think201
  4. Check if the currently installed version is 1.2.2 or below
  5. If vulnerable, click "Update Now" if an update is available, or manually download the latest version from the WordPress plugin repository and upload it
  6. After updating, verify the plugin is functioning correctly on the site
  7. Review the site to confirm the Stored XSS vulnerability is no longer exploitable

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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