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

CVE-2025-23793

HIGH · 7.1 CVSS v3.1 Published 2025-01-16
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 Ciprian Turcu Auto FTP auto-ftp allows Stored XSS.This issue affects Auto FTP: from n/a through <= 1.0.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

CSRF vulnerability in Auto FTP plugin allows attackers to inject stored XSS payloads through forged requests, affecting versions up to 1.0.1. The lack of anti-CSRF tokens enables authenticated users to unknowingly trigger malicious script storage when visiting crafted pages.

MitigationImplement anti-CSRF tokens for state-changing operations and apply proper input validation with output encoding to prevent stored XSS.

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 Auto FTP plugin is installed
    Check your website's plugin directory or plugin management interface for an FTP-related plugin named 'Auto FTP' or similar
    Affected if The Auto FTP plugin is present in the environment
  2. Determine the installed version of Auto FTP
    Access the plugin details page in your CMS/plugin management panel, or inspect the plugin header in its main PHP file to read the 'Version' field
    Affected if The installed version is 1.0.1 or lower
  3. Verify the plugin handles FTP operations
    Check if the plugin is configured to perform automated file transfer operations (upload/download) to/from remote FTP servers
    Affected if The plugin is active and configured to perform automated FTP transfers
  4. Inspect for CSRF protection on state-changing actions
    Review the plugin's source code for presence of nonces or CSRF tokens when performing file transfer operations, or test by attempting a forged request to trigger FTP actions
    Affected if The plugin lacks anti-CSRF tokens on file transfer operations
  5. Check if the plugin accepts user input for FTP paths or filenames
    Examine the plugin settings or forms where users define FTP server details, paths, or filenames
    Affected if The plugin accepts user-supplied input for FTP paths or filenames without sanitization

You are affected if the Auto FTP plugin is installed at version 1.0.1 or lower and handles FTP operations without CSRF protection on state-changing actions.

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 for state-changing operations and apply proper input validation with output encoding to prevent stored XSS.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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