dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2025-52492

HIGH · 7.5 CVSS v3.1 Published 2025-07-07
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
A vulnerability has been discovered in the firmware of Paxton Paxton10 before 4.6 SR6. The firmware file, rootfs.tar.gz, contains hard-coded credentials for the Twilio API. A remote attacker who obtains a copy of the firmware can extract these credentials. This could allow the attacker to gain unauthorized access to the associated Twilio account, leading to information disclosure, potential service disruption, and unauthorized use of the Twilio services.

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

Hard-coded Twilio API credentials embedded in the Paxton10 firmware file rootfs.tar.gz (versions before 4.6 SR6). An attacker who obtains a copy of the firmware can extract these credentials and gain unauthorized access to the associated Twilio account.

MitigationUpgrade Paxton10 firmware to version 4.6 SR6 or later. Immediately rotate any Twilio API credentials that may have been exposed in prior firmware versions.

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.1/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. Identify Paxton10 firmware version
    Check the firmware filename for the version string (e.g., rootfs.tar.gz may contain version in filename or metadata). If you can extract the firmware, look for version files or banner strings inside rootfs.tar.gz.
    Affected if The firmware version is before 4.6 SR6
  2. Extract and inspect rootfs.tar.gz for embedded credentials
    Extract the rootfs.tar.gz file and search within the extracted contents for Twilio-related strings. Use grep or a text search for terms like 'Twilio', 'API_KEY', 'AUTH_TOKEN', or look for base64-encoded credentials.
    Affected if Hard-coded Twilio API credentials or API keys are found in the firmware image
  3. Check for Twilio configuration files
    Within the extracted rootfs, look for configuration files (e.g., config, yaml, json, or shell scripts) that contain Twilio account SID, auth token, or API keys in plain text.
    Affected if Plain-text Twilio credentials are present in configuration files inside the firmware
  4. Verify running firmware version on the device
    If you have access to the Paxton10 device, check the installed firmware version through the device admin interface or by running version commands via SSH/Telnet if available.
    Affected if The device reports a firmware version earlier than 4.6 SR6

You are affected if the Paxton10 firmware version is before 4.6 SR6 and the rootfs.tar.gz contains embedded Twilio API credentials or keys.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Paxton10 firmware to version 4.6 SR6 or later. Immediately rotate any Twilio API credentials that may have been exposed in prior firmware versions.

Recommended fix High confidence

Paxton10 version 4.6 SR6 or later

  1. Obtain the Paxton10 firmware version 4.6 SR6 or later from the official Paxton support website or through authorized channels
  2. Review Paxton's official upgrade instructions for Paxton10 firmware
  3. Back up current system configuration before proceeding with the upgrade
  4. Apply the firmware upgrade following Paxton's documented procedure for Paxton10
  5. Verify the upgrade was successful by checking the firmware version in the system administration interface
  6. Confirm the new firmware version is 4.6 SR6 or later

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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