How severe is CVE-2019-3929?

CVE-2019-3929 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-3929?

Affected package information for CVE-2019-3929 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2019-3929?

No fixed release is recorded for CVE-2019-3929 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2019-3929 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2019-3929 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2019-3929 actively exploited in the wild?

Yes. There are 10 known exploit references for CVE-2019-3929, including 2 documented proof-of-concept exploits on Exploit-DB and 7 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2019-3929?

CVE-2019-3929 has an EPSS (Exploit Prediction Scoring System) score of 99.0%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2019-3929 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2019-3929 (Crestron Multiple Products Command Injection Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-04-15. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-05-06. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2019-3929?

CVE-2019-3929 is classified as Cross-site Scripting (XSS) (CWE-79), OS Command Injection (CWE-78). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2019-3929?

A Nuclei detection template exists for CVE-2019-3929, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2019-3929 published, and has it been updated?

CVE-2019-3929 was published on April 30, 2019 and was last updated on October 21, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

CISA KEV · ACTIVELY EXPLOITED

CRITICAL severity

CVE-2019-3929

CRITICAL

CVE-2019-3929 is a critical-severity (CVSS 9.8) Cross-site Scripting (XSS) vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2022-04-15) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

The Crestron AM-100 firmware 1.6.0.2, Crestron AM-101 firmware 2.7.0.1, Barco wePresent WiPG-1000P firmware 2.3.0.10, Barco wePresent WiPG-1600W before firmware 2.4.1.19, Extron ShareLink…

Published

Apr 30, 2019

Updated

Oct 21, 2025

Affected

12 products

Patched

See advisory

Exploits

10 known

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2022-04-15. Federal agencies were required to remediate by 2022-05-06.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2019-3929.

EPSS Exploitation Probability

via FIRST.org ↗

99.0%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2019-3929 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 394,803 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.

Description

The Crestron AM-100 firmware 1.6.0.2, Crestron AM-101 firmware 2.7.0.1, Barco wePresent WiPG-1000P firmware 2.3.0.10, Barco wePresent WiPG-1600W before firmware 2.4.1.19, Extron ShareLink 200/250 firmware 2.0.3.4, Teq AV IT WIPS710 firmware 1.1.0.7, SHARP PN-L703WA firmware 1.4.2.3, Optoma WPS-Pro firmware 1.0.0.5, Blackbox HD WPS firmware 1.0.0.5, InFocus LiteShow3 firmware 1.0.16, and InFocus LiteShow4 2.0.0.7 are vulnerable to command injection via the file_transfer.cgi HTTP endpoint. A remote, unauthenticated attacker can use this vulnerability to execute operating system commands as root.

Affected Products

12 products · 12 configurations

wepresent wipg-1000p firmwarebarco

1 version

2.3.0.10

wepresent wipg-1600w firmwarebarco

< 2.4.1.19

range

hd wireless presentation system firmwareblackbox

1 version

1.0.0.5

am-100 firmwarecrestron

1 version

1.6.0.2

am-101 firmwarecrestron

1 version

2.7.0.2

sharelink 200 firmwareextron

1 version

2.0.3.4

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-47924remotelinux✓ Verified

Barco WePresent - file_transfer.cgi Command Injection (Metasploit)

by Metasploit · Jan 15, 2020

Exploit-DB Source

EDB-46786webappshardware

Crestron AM/Barco wePresent WiPG/Extron ShareLink/Teq AV IT/SHARP PN-L703WA/Optoma WPS-Pro/Blackbox HD WPS/InFocus LiteShow - Remote Command Injection

by Jacob Baines · May 3, 2019

Exploit-DB Source

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2019-3929 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

How to detect CVE-2019-3929

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2019-3929 -u https://target

Template: Barco/AWIND OEM Presentation Platform - Remote Command Injection
Severity: critical
Impact: Successful exploitation of this vulnerability could lead to unauthorized remote code execution, potentially compromising the confidentiality, integrity, and availability of the affected system.
Remediation: Apply the latest security patches or updates provided by the vendor to mitigate this vulnerability.

Template by ProjectDiscovery nuclei-templates (_0xf4n9x_), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-3929 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

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

CWE Classification

CWE-79Cross-site Scripting (XSS)CWE-78OS Command Injection

Weaponization

Timeline

Disclosed

Apr 30, 2019

First exploit

Jan 15, 2020

KEV added

Apr 15, 2022

Last updated

Oct 21, 2025

Identifiers

CVE-2019-3929

References

Exploit / PoCexploit-db.com Webtenable.com Webpacketstormsecurity.com Webpacketstormsecurity.com Webcisa.gov

Related vulnerabilities

This CVE is critical severity; 1 of 8 other CVEs with CWE-79 is rated as high or higher (top: critical).

CVE-2026-114061GHSA-2rqm-h6hv-g79vCVE-2026-115897CVE-2026-114128CVE-2026-63430GHSA-c6gr-qvv4-5v3fGHSA-cg2g-xh64-v4q7CVE-2026-114130Browse all CWE-79

Provenance

Sources

OSV.devNVDCISA KEVFIRST.org (EPSS)

Last verifiedOct 21, 2025

CVE-2019-3929

Exploitation Status

Actively exploited in the wild

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

How to detect CVE-2019-3929

Frequently Asked Questions

Is CVE-2019-3929 in your dependencies?