dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-12491

HIGH · 7.5 CVSS v3.0 Published 2025-12-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/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
Senstar Symphony FetchStoredLicense Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of Senstar Symphony. Authentication is not required to exploit this vulnerability. The specific flaw exists within the implementation of FetchStoredLicense method. The issue results from the exposure of sensitive information. An attacker can leverage this vulnerability to disclose stored credentials, leading to further compromise. Was ZDI-CAN-26908.

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

The FetchStoredLicense method in Senstar Symphony improperly exposes sensitive information to unauthenticated remote attackers. This allows disclosure of stored credentials (likely license-related or system credentials) which can then be used for further system compromise.

MitigationApply vendor-supplied patch for CVE-2025-12491 immediately. If no patch available, restrict network access to Symphony server and monitor for unauthorized access attempts to the FetchStoredLicense endpoint.

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
High
Integrity
None
Availability
None

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

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 Senstar Symphony installation
    Locate Senstar Symphony installation directory, typically under C:\Program Files\Senstar\Symphony or /opt/senstar/symphony. Check for symphony.exe or symphony service.
    Affected if Senstar Symphony software is present on the system
  2. Identify installed Symphony version
    Check the application version through the UI (Help > About), or examine version info of the main executable (symphony.exe) via right-click Properties > Details, or check installation logs for version strings.
    Affected if Installed version falls within unpatched range and matches vulnerable release
  3. Verify FetchStoredLicense endpoint exposure
    Review API endpoint configuration or web service settings in Symphony's config files (typically in conf/ or config/ subdirectories). Check for exposed web service methods accessible without authentication.
    Affected if FetchStoredLicense method is exposed via HTTP/HTTPS without requiring authentication
  4. Check network accessibility of Symphony services
    Identify listening ports (typically 8080, 8443, or configured web service ports) using netstat -an | findstr LISTENING or equivalent. Verify if external network access is permitted through firewall rules.
    Affected if Symphony web services are reachable from untrusted networks without proper access controls
  5. Inspect credential storage configuration
    Examine Symphony configuration files for license storage settings or credential encryption mechanisms. Look for files named license.*, credentials.*, or similar in the configuration directory.
    Affected if Credentials are stored in plaintext or with weak encryption accessible to unauthenticated requests

A user is affected if Senstar Symphony is installed with the FetchStoredLicense endpoint exposed to unauthenticated network access, allowing retrieval of stored credentials.

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

Apply vendor-supplied patch for CVE-2025-12491 immediately. If no patch available, restrict network access to Symphony server and monitor for unauthorized access attempts to the FetchStoredLicense endpoint.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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