dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-40757

MEDIUM · 5.3 CVSS v3.1 Published 2025-09-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 identified in APOGEE PXC Series (BACnet) (All versions), APOGEE PXC Series (P2 Ethernet) (All versions), TALON TC Series (BACnet) (All versions). Affected devices connected to the network allow unrestricted access to sensitive files, such as databases. This could allow an attacker to download encrypted .db file containing passwords.

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

Affected Schneider Electric building automation devices (APOGEE PXC Series and TALON TC Series) contain an information disclosure vulnerability allowing unauthenticated network attackers to download sensitive database files (.db) containing encrypted password hashes. This appears to stem from missing or insufficient access controls on the embedded web server/file system.

MitigationImplement network segmentation to isolate building automation devices from untrusted networks, configure firewall rules to restrict access to management interfaces, and review vendor guidance for compensating controls since no patch information is provided for these legacy devices.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Identify device model and series
    Access the device management interface or use network discovery to confirm the exact model (e.g., PXC-8000, PXC-600) and verify it belongs to the APOGEE PXC Series or TALON TC Series product line.
    Affected if Device is an APOGEE PXC Series or TALON TC Series controller.
  2. Confirm web server is network-accessible
    Attempt to reach the device's embedded web server via HTTP/HTTPS from an untrusted network segment (e.g., outside the building automation VLAN). Check if TCP ports 80, 443, or custom web service ports respond.
    Affected if The web interface is reachable from untrusted networks without network segmentation.
  3. Test for unauthenticated .db file access
    Use a web browser or curl/wget to attempt direct requests to common database file paths on the web server, such as /database.db, /config.db, /system.db, or similar .db file extensions, without providing any authentication credentials.
    Affected if The web server allows downloading .db files without authentication.
  4. Verify password hash exposure
    If .db files are accessible, open or parse them to confirm they contain password hash data (look for hashed credentials, user account records, or encrypted password fields).
    Affected if Downloaded .db files contain encrypted password hashes or credential data.
  5. Review file system access controls
    Check the device configuration or documentation for web server access control settings. Determine if there are missing or disabled restrictions on file system directories accessible via the web interface.
    Affected if Access controls on the embedded web server are missing, disabled, or insufficiently configured.

A user is affected if they have an APOGEE PXC or TALON TC device with its web interface exposed to untrusted networks and the server permits unauthenticated access to .db files containing password hashes.

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 network segmentation to isolate building automation devices from untrusted networks, configure firewall rules to restrict access to management interfaces, and review vendor guidance for compensating controls since no patch information is provided for these legacy devices.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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