CVE-2022-33941Network attack vector

Unauthenticated command injection via XMLRPC POST

Published Sep 8, 2022 · Updated Aug 3, 2024

Command injection in PowerCMS XMLRPC API through 6.021 allows remote attackers to execute Perl scripts and OS commands via crafted POST messages. The XMLRPC handler processes attacker-controlled POST message content as executable Perl, which enables operating-system command execution through the script context. Exploitation requires the XMLRPC API to be enabled and reachable; the published assessment requires no authentication or user interaction, and the consequence includes arbitrary code execution with the server process's privileges.

CVSS severity9.8
Critical
EPSS probability1.86%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Command injection in PowerCMS XMLRPC API through 6.021 allows remote attackers to execute Perl scripts and OS commands via crafted POST messages. The XMLRPC handler processes attacker-controlled POST message content as executable Perl, which enables operating-system command execution through the script context. Exploitation requires the XMLRPC API to be enabled and reachable; the published assessment requires no authentication or user interaction, and the consequence includes arbitrary code execution with the server process's privileges.

The record

CVE
CVE-2022-33941
Published
Sep 8, 2022
Updated
Aug 3, 2024
Vendor
Alfasado Inc.
Product
PowerCMS
Classifications
CWE-74, CWE-78, T1059.006
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Sep 8, 2022CVE publishedPublication date reported by the CVE source.
  2. Aug 3, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=PowerCMS 6.021 and earlier (PowerCMS 6 Series), PowerCMS 5.21 and earlier (PowerCMS 5 Series), PowerCMS 4.51 and earlier (PowerCMS 4 Series), and PowerCMS 3 Series and earlier which are unsupported (End-of-Life, EOL)

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Alfasado Inc. · PowerCMSversion=PowerCMS 6.021 and earlier (PowerCMS 6 Series), PowerCMS 5.21 and earlier (PowerCMS 5 Series), PowerCMS 4.51 and earlier (PowerCMS 4 Series), and PowerCMS 3 Series and earlier which are unsupported (End-of-Life, EOL)

Published CVSS scores

7.5JPCERT/CCAV:N/AC:L/Au:N/C:P/I:P/A:P
9.8JPCERT/CCCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-74Improper Neutralization of Special Elements
CWE-78OS Command Injection
T1059.006Command and Scripting Interpreter: Perl

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo