dbcve.org
Easybuilder ProApplication · Weintek

CVE-2023-0104

HIGH · 7.8 CVSS v3.1 Published 2023-02-22
Fix available
A fix is available. Upgrade to 6.07.02.480 / 6.08.01.350 or later.
See remediation →
81/100
Remediation priority · High
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
The listed versions for Weintek EasyBuilder Pro are vulnerable to a ZipSlip attack caused by decompiling a malicious project file. This may allow an attacker to gain control of the user’s computer or gain access to sensitive data.  

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

Weintek EasyBuilder Pro contains a ZipSlip vulnerability in its project file decompilation logic. When processing a malicious project file (zip archive), the software fails to properly validate file paths in archive entries, allowing directory traversal via '..' sequences in filenames. This enables arbitrary file write to filesystem locations outside the intended extraction directory, potentially leading to remote code execution or sensitive data access.

MitigationDo not open untrusted or unverified EasyBuilder Pro project files; only use project files from trusted sources. Apply vendor patches when released.

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
Easybuilder ProApplication
Affected:< 6.07.02.480>= 6.08.01.190, < 6.08.01.350

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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. Locate Weintek EasyBuilder Pro installation
    Check common installation directories such as C:\Program Files\Weintek\EasyBuilder Pro or C:\Program Files (x86)\Weintek\EasyBuilder Pro. On Windows, also check the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Weintek or HKEY_CURRENT_USER\SOFTWARE\Weintek for the installed path.
    Affected if Weintek EasyBuilder Pro software is found on the system
  2. Identify installed version number
    Navigate to the installation directory and locate a version file, or right-click the EasyBuilder Pro executable and select Properties > Details to view the File Version. The version may also appear in the software's About or Help menu when running the application.
    Affected if A version number cannot be determined or differs from the file properties
  3. Compare version against affected ranges
    If version is found, compare it to the following vulnerable ranges: any version less than 6.07.02.480, OR any version from 6.08.01.190 up to but not including 6.08.01.350. Versions 6.07.02.480 through 6.08.01.189 are not affected, as are versions 6.08.01.350 and later.
    Affected if Installed version falls within < 6.07.02.480 OR >= 6.08.01.190 AND < 6.08.01.350

The environment is affected if Weintek EasyBuilder Pro is installed and the version number matches either of the two vulnerable ranges.

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 6.07.02.480 / 6.08.01.350 or later
Fixed in 6.07.02.4806.08.01.350
Interim mitigation

Do not open untrusted or unverified EasyBuilder Pro project files; only use project files from trusted sources. Apply vendor patches when released.

Recommended fix Moderate confidence

EasyBuilder Pro 6.07.02.480 or later (for old branch); EasyBuilder Pro 6.08.01.350 or later (for 6.08.x branch)

  1. 1. Identify the current installed version of Weintek EasyBuilder Pro
  2. 2. For versions before 6.07.02.480: Upgrade to version 6.07.02.480 or later
  3. 3. For versions 6.08.01.190 through 6.08.01.349: Upgrade to version 6.08.01.350 or later
  4. 4. Obtain the updated installer from the official Weintek website or trusted distribution channel
  5. 5. Backup any existing project files before performing the upgrade
  6. 6. Run the installer with administrator privileges
  7. 7. After upgrade, verify the new version in Help > About in EasyBuilder Pro
  8. 8. Test that legitimate project files open correctly after the update
Caveat Review release notes for any project file format changes or feature modifications between versions

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

Fix this in Easybuilder Pro Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
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,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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