dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-11620

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
A security flaw has been discovered in TOTOLINK EX200 4.0.3c.7646. This affects an unknown function of the file /etc/vsftpd.conf of the component vsftpd. The manipulation results in least privilege violation. It is possible to launch the attack remotely. The exploit has been released to the public and may be used for attacks.

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 least privilege violation vulnerability exists in the vsftpd FTP server configuration (/etc/vsftpd.conf) on TOTOLINK EX200 router firmware version 4.0.3c.7646. The misconfiguration allows unauthorized remote attackers to exploit the FTP service with elevated privileges beyond what should be permitted, potentially enabling unauthorized file access or system compromise. The public availability of the exploit increases the likelihood of targeted attacks.

MitigationUpdate to the latest TOTOLINK EX200 firmware when available from the vendor; as an interim control, disable the vsftpd service if not required, or restrict access via firewall rules to prevent external FTP connections.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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. Confirm device is TOTOLINK EX200 router
    Access router admin interface or check device label/model number to verify the model is EX200
    Affected if Device is not a TOTOLINK EX200 router - this vulnerability only affects that specific model
  2. Check firmware version
    Log into router admin interface (typically 192.168.0.1 or 192.168.1.1) and navigate to Status or System > Firmware version to see installed firmware
    Affected if Firmware version is 4.0.3c.7646 (exact match based on provided data)
  3. Locate vsftpd configuration file
    Access router via SSH or Telnet (if enabled) and check for /etc/vsftpd.conf file existence, or extract firmware binary and search for vsftpd.conf
    Affected if File /etc/vsftpd.conf does not exist on the device - the vulnerability requires this specific configuration file to be present
  4. Inspect vsftpd.conf for privilege misconfiguration
    View contents of /etc/vsftpd.conf and examine settings related to user privileges, local user access, and permission controls. Look for configurations that allow users to access files outside their home directory or bypass intended restrictions
    Affected if The vsftpd.conf contains settings that violate least privilege principles - such as misconfigured user access controls, improper directory permissions, or settings allowing unintended file system access
  5. Verify FTP service is enabled
    Check if FTP server is running on the router - look for vsftpd process in running processes or check if port 21 is listening
    Affected if FTP service is actively running and accessible over the network - the vulnerability requires network access to the FTP server to be exploitable

User is affected if they have a TOTOLINK EX200 router running firmware version 4.0.3c.7646 with vsftpd enabled and a misconfigured /etc/vsftpd.conf file that violates least privilege principles.

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

Update to the latest TOTOLINK EX200 firmware when available from the vendor; as an interim control, disable the vsftpd service if not required, or restrict access via firewall rules to prevent external FTP connections.

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-2026-11620 — 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-2026-11620 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