Security Resilience

CVE-2023-49213

RCE in Ironmansoftware Powershell Universal 3.0.0 – 3.10.2

Published
23 November 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.021 82th percentile
Risk Priority 68 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-49213 is a high-severity Command Injection (CWE-77) vulnerability in Ironmansoftware Powershell Universal. Its CVSS base score is 8.8 (High).

Operationally, ranked in the top 18% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

The API endpoints in Ironman PowerShell Universal 3.0.0 through 4.2.0 allow remote attackers to execute arbitrary commands via crafted HTTP requests if a param block is used, due to invalid sanitization of input strings. The fixed versions are 3.10.2, 4.1.10,…

more

and 4.2.1.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-3277Same product: Ironmansoftware Powershell Universal
CVE-2026-8694Same product: Ironmansoftware Powershell Universal
CVE-2026-4064Same product: Ironmansoftware Powershell Universal
CVE-2026-3563Same product: Ironmansoftware Powershell Universal
CVE-2026-0618Same product: Ironmansoftware Powershell Universal
CVE-2025-56425Shared CWE-77
CVE-2023-32073Shared CWE-77
CVE-2023-34233Shared CWE-77
CVE-2024-4578Shared CWE-77
CVE-2025-46176Shared CWE-77

Affected Assets

ironmansoftware
powershell universal
4.2.0 · 3.0.0 — 3.10.2 · 4.1.0 — 4.1.10

Mitigating Controls

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

blocks

A.8.25 mandates secure SDLC practices including secure coding guidelines, security requirements, checkpoints, testing (scans/penetration), and developer training that reduce command injection defects, but leaves a minority slice (e.g. incomplete implementation of those practices, outsourced development without full assurance, or post-SDLC changes) where the weakness can still arise and be exploitable.

blocks

Application security requirements explicitly call for controls against injection flaws including command injection.

blocks

A.8.27 mandates security-by-design principles (e.g. distrust external input, secure session control, data validation/sanitization, least privilege) and design reviews that can stop command injection from being introduced, but this is only a minority slice of CWE-77 because the weakness can still arise in code that bypasses those principles, in non-reviewed components, or in runtime injection vectors the architecture review does not reach.

prevents

Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.

finds

Security testing in development catches command-injection vulnerabilities before release.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-77, a class-level weakness, and none of its children carries one either.

References