dbcve.org
Dext5 EditorApplication · Dext5

CVE-2020-7864

CRITICAL · 9.8 CVSS v3.1 Published 2021-06-15
Fix available
A fix is available. Upgrade to 3.5.1405747.1100.03 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Parameter manipulation can bypass authentication to cause file upload and execution. This will execute the remote code. This issue affects: Raonwiz DEXT5Editor versions prior to 3.5.1405747.1100.03.

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 · high confidence

In Raonwiz DEXT5Editor versions prior to 3.5.1405747.1100.03, an authentication bypass vulnerability exists where parameter manipulation allows attackers to bypass authentication mechanisms, upload arbitrary files to the server, and execute them remotely, achieving full remote code execution.

MitigationUpgrade DEXT5Editor to version 3.5.1405747.1100.03 or later. If immediate patching is not feasible, implement network-level access controls to restrict exposure of the editor's upload endpoints and deploy a WAF to detect and block malicious parameter manipulation attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Dext5 EditorApplication
Affected:< 3.5.1405747.1100.03

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
High
Integrity
High
Availability
High

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

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 DEXT5Editor version
    Locate the DEXT5Editor installation and check its version number. This is typically found in the assembly metadata, version file, or the main DLL/assembly loaded by the web application (often named dext5editor.dll or similar). Compare the found version to the affected range: versions prior to 3.5.1405747.1100.03 are vulnerable.
    Affected if The installed version is less than 3.5.1405747.1100.03.
  2. Determine if upload functionality is exposed
    Identify whether DEXT5Editor's upload endpoints are accessible from the network. Check web application configuration files (web.config) and routing configuration for paths such as /upload/, /dext5upload/, or similar upload handlers provided by DEXT5Editor.
    Affected if Upload handlers are exposed without proper network restrictions or authentication enforcement.
  3. Inspect authentication mechanism for upload handlers
    Review the authentication configuration for DEXT5Editor upload endpoints. Check if the upload modules/handlers properly validate authentication tokens or session state before allowing file operations.
    Affected if Upload endpoints can be accessed without valid authentication or allow parameter manipulation to bypass auth checks.
  4. Check for file upload validation
    Examine the server-side validation logic for file uploads. Determine if the upload handler properly validates file types, contents, and extension restrictions before saving files.
    Affected if The upload endpoint accepts arbitrary file types without proper validation, allowing potential malicious file upload.

A user is affected if DEXT5Editor version is below 3.5.1405747.1100.03 AND the upload functionality is exposed to potentially untrusted users without adequate authentication controls.

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
Upgrade available Upgrade to 3.5.1405747.1100.03 or later
Fixed in 3.5.1405747.1100.03
Interim mitigation

Upgrade DEXT5Editor to version 3.5.1405747.1100.03 or later. If immediate patching is not feasible, implement network-level access controls to restrict exposure of the editor's upload endpoints and deploy a WAF to detect and block malicious parameter manipulation attempts.

Recommended fix High confidence

Dext5 Editor version 3.5.1405747.1100.03 or later

  1. 1. Identify all deployed instances of Dext5 Editor in your environment
  2. 2. Verify the current version of Dext5 Editor installed on each instance
  3. 3. Download Dext5 Editor version 3.5.1405747.1100.03 or later from the official vendor (Raonwiz)
  4. 4. Review the vendor's upgrade documentation and release notes for the target version
  5. 5. Create a backup of the current Dext5 Editor installation and configuration
  6. 6. Deploy the updated version in a staging environment to verify compatibility
  7. 7. Apply the upgrade to production environments following vendor migration procedures
  8. 8. Verify the upgrade was successful by checking the new version number
Caveat Review vendor release notes for any configuration changes or compatibility impacts between your current version and 3.5.1405747.1100.03

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

Fix this in Dext5 Editor Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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