CVE-2019-25243: FaceSentry 6.4.8 Authenticated Remote Command Injection via Ping Test
FaceSentry 6.4.8 contains an authenticated remote command injection vulnerability in pingTest.php and tcpPortTest.php scripts. Attackers can exploit unsanitized input parameters to inject and execute arbitrary shell commands with root privileges by manipulating the 'strInIP' and 'strInPort' parameters.
Security readout for executives and security teams
Plain-English summary
FaceSentry access control systems have an authenticated command injection flaw. A user with access to the affected web functions could run operating system commands as root, potentially taking full control of the device that manages physical access functions.
Executive priority
Treat this as high priority for any deployed FaceSentry system because compromise could affect both IT security and physical access operations. Prioritize identification, isolation, and vendor-supported remediation.
Technical view
CVE-2019-25243 is CWE-78 command injection in FaceSentry pingTest.php and tcpPortTest.php. Unsanitized strInIP and strInPort parameters can allow arbitrary shell command execution with root privileges. CVSS 3.1 is 8.8: network exploitable, low privileges required, no user interaction.
Likely exposure
Exposure applies to iWT FaceSentry Access Control System versions 6.4.8 build 264, 5.7.2 build 568, and 5.7.0 build 539. Risk is highest where authenticated users can reach the management or diagnostic web interface from less-trusted networks.
Exploitation context
The source bundle cites public ExploitDB and Zero Science Lab references. It does not show CISA KEV listing or confirmed active exploitation. Exploitation requires authenticated access, but successful abuse can provide root-level command execution on the appliance.
Researcher notes
The strongest evidence is the CVE record plus third-party disclosure and public exploit reference. Patch availability is not provided in the source bundle, so remediation should not assume a specific fixed version without vendor confirmation.
Mitigation direction
Check iWT or vendor guidance for fixed firmware or supported upgrade paths.
Restrict FaceSentry management interfaces to trusted administrative networks only.
Remove unnecessary user accounts and review who can access diagnostics pages.
Disable or limit diagnostic test functions if vendor-supported.
Monitor affected systems for unexpected diagnostic script usage.
Validation and detection
Inventory FaceSentry appliances and record exact firmware and build versions.
Confirm whether pingTest.php and tcpPortTest.php are present and reachable.
Review access controls for the web management interface.
Check logs for suspicious use of diagnostic test pages.
Document vendor patch status if available from iWT support.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.