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

CVE-2024-38789

MEDIUM · 5.4 CVSS v3.1 Published 2025-01-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
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 Marco Milesi Telegram Bot & Channel telegram-bot allows Cross Site Request Forgery.This issue affects Telegram Bot & Channel: from n/a through <= 3.8.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

This is a Cross-Site Request Forgery (CSRF) vulnerability in the Marco Milesi Telegram Bot & Channel plugin. CSRF attacks trick authenticated users into unknowingly submitting malicious requests to a web application, potentially allowing attackers to perform unauthorized actions through the Telegram bot integration.

MitigationImplement anti-CSRF tokens on all state-changing operations and validate these tokens server-side before processing requests. Additionally, set the SameSite attribute on session cookies to mitigate CSRF attacks.

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
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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 Marco Milesi Telegram Bot plugin is installed
    Look for the plugin files in your WordPress plugins directory, typically in wp-content/plugins/ directory, searching for folders containing 'telegram' and 'marco' or 'milesi' in the name
    Affected if The plugin folder exists in the installation
  2. Determine the installed plugin version
    Check the plugin's main PHP file for a version comment or header, often found in the main plugin file under 'Version:' or '$version' variable
    Affected if The version is unknown or falls within a range specified by the vendor advisory (no specific version range provided in CVE)
  3. Inspect state-changing operations for CSRF protection
    Review the plugin's PHP source code for form submissions and AJAX actions that modify data (such as bot settings, message sending, or channel configuration). Look for the presence of nonce tokens or CSRF tokens in these operations
    Affected if State-changing functions lack nonce verification or token validation
  4. Check cookie SameSite attribute configuration
    Examine the application session cookie headers or configuration to verify if the SameSite attribute is set to 'Strict' or 'Lax'
    Affected if SameSite attribute is missing or set to 'None' on session cookies

You are affected if the Marco Milesi Telegram Bot & Channel plugin is installed and handles sensitive operations without anti-CSRF token validation on state-changing requests.

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 operations and validate these tokens server-side before processing requests. Additionally, set the SameSite attribute on session cookies to mitigate CSRF attacks.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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