dbcve.org
Command InjectionWeakness · CWE-77

CVE-2025-4678

HIGH · 7.0 CVSS v4.0 Published 2025-06-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
79/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Neutralization of Special Elements in the chromium_path variable may allow OS command injection. This issue affects Pandora ITSM 5.0.105.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A command injection vulnerability exists in Pandora ITSM 5.0.105 where the chromium_path variable is not properly sanitized, allowing an attacker to inject malicious OS commands through this input field.

MitigationImplement strict input validation and proper escaping of special characters in the chromium_path variable before using it in any system calls. Use allowlist validation to ensure only valid file paths are accepted.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
Authentication
None
User interaction
None
Scope
N

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:L/VA:L/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:N/R:U/V:D/RE:M/U:Green

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Pandora ITSM installation and version
    Locate the Pandora ITSM installation directory and check the version file, typically found in the main installation path (e.g., looking for a version file, about page, or running 'pandora_itsm --version' if available)
    Affected if The installed version is 5.0.105 or earlier unpatched versions
  2. Locate chromium_path configuration
    Search configuration files for the 'chromium_path' parameter, typically in settings, preferences, or PDF-related configuration files within the Pandora ITSM config directory
    Affected if A chromium_path setting exists in the configuration
  3. Verify chromium_path is accessible to users
    Check if the web interface or configuration panel allows modification of the chromium_path setting, and determine if authenticated users (especially low-privilege users) can access this setting
    Affected if The chromium_path field is editable through the application interface
  4. Check for command execution context
    Identify if chromium_path is used in system calls or shell execution commands (check application logs, code references, or documentation for PDF generation features that invoke a browser binary)
    Affected if chromium_path is used in any system() or shell execution function without sanitization

You are affected if Pandora ITSM version 5.0.105 is installed and the chromium_path configuration setting is accessible and can be modified without proper input validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and proper escaping of special characters in the chromium_path variable before using it in any system calls. Use allowlist validation to ensure only valid file paths are accepted.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-4678 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-4678 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data