CVE-2019-12811
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 · uneditedActiveX Control in MyBuilder before 6.2.2019.814 allow an attacker to execute arbitrary command via the ShellOpen method. This can be leveraged for code execution
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 confidenceAn ActiveX control in MyBuilder versions prior to 6.2.2019.814 contains a vulnerability in the ShellOpen method that allows unauthenticated attackers to execute arbitrary commands on the affected system, leading to full code execution. The vulnerability stems from improper validation of input passed to the ShellOpen method.
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< 6.2.2019.814CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate MyBuilder installationSearch for MyBuilder executable (mybuilder.exe) in common installation directories such as C:\Program Files\Activesoft\MyBuilder or C:\Program Files (x86)\Activesoft\MyBuilder, or check the Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\Activesoft\MyBuilder for the InstallPath value.Affected if MyBuilder is found installed on the system.
-
Determine installed MyBuilder versionRight-click on the mybuilder.exe file, select Properties, and read the Product Version field from the Details tab. Alternatively, run mybuilder.exe and check its help-about dialog for the exact version number.Affected if The version shown is less than 6.2.2019.814.
-
Check for ActiveX control registrationOpen the Windows Registry Editor and search for the MyBuilder ActiveX control CLSID under HKEY_CLASSES_ROOT\CLSID. The control is typically registered as an ActiveX component associated with MyBuilder.Affected if The ActiveX control CLSID is present in the registry, indicating the control is registered.
-
Verify ShellOpen method availabilityUsing a script or registry query, confirm the ShellOpen method exists in the ActiveX control's interface definition. This can be done by examining the type library or COM interface entries for the MyBuilder control in the registry.Affected if The ShellOpen method is exposed by the registered ActiveX control.
A user is affected if MyBuilder is installed with a version prior to 6.2.2019.814 and the ActiveX control with the ShellOpen method is registered on the system.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.2.2019.814
Update MyBuilder to version 6.2.2019.814 or later to obtain the patched ActiveX control. If immediate patching is not feasible, disable the MyBuilder ActiveX control or restrict its use in untrusted contexts/browser zones as a temporary compensating control.
6.2.2019.814 or later
- Verify the current MyBuilder version installed on the system
- Download MyBuilder version 6.2.2019.814 or later from the official vendor source
- Create a backup of any critical data or configurations associated with MyBuilder
- Uninstall the current vulnerable version of MyBuilder
- Install the fixed version (6.2.2019.814 or later)
- Verify the installation was successful and the version number matches the fixed release
- Test that the application functions normally after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12811 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-12811 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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