dbcve.org
Industrial Automation AprolApplication · Br Automation

CVE-2019-19876

CRITICAL · 9.8 CVSS v3.1 Published 2020-11-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
An issue was discovered in B&R Industrial Automation APROL before R4.2 V7.08. An EnMon PHP script was vulnerable to SQL injection, a different vulnerability than CVE-2019-10006.

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

SQL injection vulnerability in the EnMon PHP script of B&R Industrial Automation APROL allows remote attackers to inject malicious SQL queries. The vulnerability affects versions prior to R4.2 V7.08 and can be exploited without authentication given its critical CVSS score of 9.8.

MitigationApply vendor patch for APROL R4.2 V7.08 or later. If immediate patching is not possible, implement input validation and web application firewall rules to filter SQL injection payloads at the perimeter.

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
Industrial Automation AprolApplication
Affected:< r4.2

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. Confirm APROL installation
    Identify if B&R Industrial Automation APROL is installed on the system by looking for APROL-related services, processes, or installation directories.
    Affected if APROL is present on the system
  2. Check APROL version
    Determine the installed APROL version and compare it against the vulnerable range: versions prior to R4.2 V7.08. Look for version files, About dialogs, or system information within the APROL installation.
    Affected if The installed version is prior to R4.2 V7.08 or the version cannot be determined to be at or above V7.08
  3. Locate EnMon PHP script
    Search for the EnMon PHP script within the APROL web directory structure. The vulnerability exists specifically in this PHP component.
    Affected if The EnMon PHP script is found in the APROL installation
  4. Verify web interface exposure
    Check if the APROL web server (typically on ports 80/443 or custom ports) is accessible from network locations. Since this vulnerability can be exploited without authentication, external accessibility increases risk.
    Affected if The EnMon web endpoint is accessible remotely without authentication
  5. Inspect HTTP access logs
    Review web server access logs for suspicious SQL injection patterns in requests targeting EnMon endpoints. Look for common SQLi payloads like UNION SELECT, OR 1=1, or quotes and semicolons in query parameters.
    Affected if SQL injection attempt patterns are found in logs for EnMon requests

The environment is affected if APROL with the EnMon component is installed and the version is prior to R4.2 V7.08, with the web interface accessible to potential attackers.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch for APROL R4.2 V7.08 or later. If immediate patching is not possible, implement input validation and web application firewall rules to filter SQL injection payloads at the perimeter.

Recommended fix Moderate confidence

APROL R4.2 V7.08 or later

  1. 1. Identify the current APROL version installed in the system
  2. 2. Review the B&R Industrial Automation product release notes for R4.2 V7.08 or later for upgrade procedures
  3. 3. Plan and schedule maintenance window for the upgrade process
  4. 4. Perform a complete backup of the APROL system including databases and configurations
  5. 5. Follow B&R official upgrade documentation to update to R4.2 V7.08 or later release
  6. 6. After upgrade, verify the EnMon PHP script functionality and confirm SQL injection vulnerability is remediated
  7. 7. Validate system operation and monitor for any anomalies

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

Fix this in Industrial Automation Aprol Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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