Threat Signal Report

Command Injection Vulnerability (CVE-2022-46169) in Cacti Being Exploited in the Wild

description-logo Description

FortiGuard Labs is aware of a report that a recently patched vulnerability in the Cacti network monitoring and management suite is being exploited in the wild. The vulnerability (CVE-2022-46169) is a command injection vulnerability that allows a remote, unauthenticated user to execute arbitrary code on a server running vulnerable version of Cacti.

Why is this Significant?

This is significant because, although recently patched, CVE-2022-46169 is reported to have been exploited in the wild. The vulnerability is in Cacti, which is an open-source software for monitoring network devices and graphically displaying collected information.

What is CVE-2022-46169?

CVE-2022-46169 is a vulnerability in the Cacti network monitoring and management that a remote, unauthenticated attacker could exploit by sending a crafted HTTP request. Successful exploitation could result in arbitrary system command execution under the context of the target system.

The vulnerability is rated critical and has a CVSS score of 9.8.

Has the Vendor Released an Advisory for CVE-2022-46169?

Yes, the advisory is publicly available. See the Appendix for a link to "Unauthenticated Command Injection".

What Version of Cacti is Vulnerable?

The advisory released by Cacti lists 1.2.22 as a vulnerable version.

Has the Vendor Released a Patch for CVE-2022-46169?

Yes, the patch was released in v1.2.23 and v1.3.0 on December 5, 2022.

What is the Status of Protection?

FortiGuard Labs has the following IPS signature in place for

  • Cacti.remote_agent.php.Remote.Command.Execution (default action is set to "pass")



Tweet (@Shadowserver)

Unauthenticated Command Injection (Cacti)

CVE-2022-46169 (MITRE)


Traffic Light Protocol

Color When Should it Be used? How may it be shared?


Not for disclosure, restricted to participants only.
Sources may use TLP:RED when information cannot be effectively acted upon by additional parties, and could lead to impacts on a party's privacy, reputation, or operations if misused. Recipients may not share TLP:RED information with any parties outside of the specific exchange, meeting, or conversation in which it was originally disclosed. In the context of a meeting, for example, TLP:RED information is limited to those present at the meeting. In most circumstances, TLP:RED should be exchanged verbally or in person.


Limited disclosure, restricted to participants’ organizations.
Sources may use TLP:AMBER when information requires support to be effectively acted upon, yet carries risks to privacy, reputation, or operations if shared outside of the organizations involved. Recipients may only share TLP:AMBER information with members of their own organization, and with clients or customers who need to know the information to protect themselves or prevent further harm. Sources are at liberty to specify additional intended limits of the sharing: these must be adhered to.


Limited disclosure, restricted to the community.
Sources may use TLP:GREEN when information is useful for the awareness of all participating organizations as well as with peers within the broader community or sector. Recipients may share TLP:GREEN information with peers and partner organizations within their sector or community, but not via publicly accessible channels. Information in this category can be circulated widely within a particular community. TLP:GREEN information may not be released outside of the community.


Disclosure is not limited.
Sources may use TLP:WHITE when information carries minimal or no foreseeable risk of misuse, in accordance with applicable rules and procedures for public release. Subject to standard copyright rules, TLP:WHITE information may be distributed without restriction.