HighPublic exploit

OS Command Injection in Pandora ITSM 5.0.105 backup name field

IdentifiersCVE-2025-4653CWE-78

CVE-2025-4653 is an OS command injection vulnerability in Pandora ITSM 5.0.105. According to the provided content, the issue is caused by improper neutralization of special elements in the backup name field, allowing attacker-controlled input to be interpreted as part of an operating system command. If the application passes the backup name value to a shell or command execution context without sufficient sanitization or safe argument handling, an attacker may inject arbitrary commands.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation may allow execution of arbitrary operating system commands in the security context of the Pandora ITSM application or the underlying service account. This can lead to compromise of the affected host, unauthorized access to data handled by the application, modification or deletion of files, service disruption, and potential follow-on actions depending on the privileges available to the process.

Mitigation

If you can’t patch tonight, do this now.

As interim mitigation, restrict access to functionality that accepts the backup name field to trusted administrative users only, disable or limit backup features if operationally feasible, and prevent the application from invoking shell commands with user-controlled input. Apply strong input filtering for backup names, monitor for suspicious command execution from the Pandora ITSM process, and run the service with the least privileges possible to reduce impact.

Remediation

Patch, then assume compromise.

Upgrade to a fixed version from the vendor if available. The vulnerable code handling the backup name field should be corrected to avoid passing untrusted input into shell command contexts, using strict input validation, allowlisting of permitted characters, and safe APIs that do not invoke a shell. Review vendor advisories and release notes for the specific patched version addressing CVE-2025-4653.

PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.

VALID 1 / 1 TOTALView more in app

pandora_itsm_auth_rce_cve_2025_4653.rbMaturityWeaponizedFrameworkmetasploitVerified exploit

This repository contains a single Metasploit module targeting a command injection vulnerability (CVE-2025-4653) in Pandora ITSM Enterprise editions up to 5.0.105. The exploit leverages a flaw in the backup function's 'name' parameter, allowing authenticated attackers to inject and execute arbitrary system commands. The module supports two main attack paths: (1) using valid or default admin credentials for the Pandora ITSM web application, or (2) exploiting default database credentials to create a new admin user, then authenticating to the web interface. The exploit is delivered via HTTP requests to the Pandora ITSM web application (default path '/pandoraitsm'), and may require access to the MySQL database (default port 3306). The default payload is a reverse shell (meterpreter), but any compatible command payload can be used. The module is operational and suitable for real-world exploitation, provided the attacker has the necessary credentials or can leverage the default password weakness. The code is well-structured, with clear separation of database and web authentication logic, and includes error handling for various failure scenarios.

Disclosed Jun 10, 2025rubynetwork

ACTIVITY FEED

Recent activity

3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

3 SOURCESView more in app

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity3