dbcve.org
Command InjectionWeakness · CWE-77

CVE-2025-1546

HIGH · 7.3 CVSS v3.1 Published 2025-02-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/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
A vulnerability has been found in BDCOM Behavior Management and Auditing System up to 20250210 and classified as critical. Affected by this vulnerability is the function log_operate_clear of the file /webui/modules/log/operate.mds. The manipulation of the argument start_code leads to os command injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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 · moderate confidence

BDCOM Behavior Management and Auditing System contains an OS command injection vulnerability in the log_operate_clear function within /webui/modules/log/operate.mds. The start_code parameter is not properly sanitized before being used in OS command execution, allowing an attacker to inject arbitrary shell commands remotely.

MitigationSince the vendor has not responded to disclosure, implement network segmentation to restrict access to the affected system, and consider deploying WAF rules to filter malicious input patterns for the start_code parameter until a vendor patch is available.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 BDCOM Behavior Management and Auditing System is installed
    Locate the installation directory or identify the running service. Check for the presence of /webui/modules/log/operate.mds file in the web root. If running as a service, verify the process name matches the BDCOM system.
    Affected if The system has the BDCOM Behavior Management and Auditing System deployed and the webui module path exists.
  2. Verify the vulnerable endpoint is accessible
    Attempt to access the affected URL path: /webui/modules/log/operate.mds via HTTP/HTTPS. Check if the web interface responds to requests targeting this module.
    Affected if The /webui/modules/log/operate.mds endpoint returns a valid response, indicating the module is loaded and active.
  3. Identify if the log_operate_clear function is exposed
    Send a request to the operate.mds module with a test parameter. The vulnerable function processes the start_code parameter. Review the application's routing to confirm log_operate_clear can be invoked.
    Affected if The log_operate_clear function is callable and accepts the start_code parameter through the web interface.
  4. Check for signs of command injection exploitation
    Review web server access logs and application logs for anomalous requests containing shell metacharacters (like ;, |, &, $(), ``) in the start_code parameter. Look for unexpected command execution patterns.
    Affected if Logs contain requests with shell command patterns in the start_code parameter, or unexpected command execution artifacts.

A system is affected if it runs the BDCOM Behavior Management and Auditing System with the /webui/modules/log/operate.mds module accessible and the start_code parameter accepted by the log_operate_clear function.

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

Since the vendor has not responded to disclosure, implement network segmentation to restrict access to the affected system, and consider deploying WAF rules to filter malicious input patterns for the start_code parameter until a vendor patch is available.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1546 — 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-1546 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