{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-52492 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-52492 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-52492 is a high-severity vulnerability in n/a, published on 7 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-52492 and fix it if it is affected.\n\nWhat it is: CVE-2025-52492 is a high-severity vulnerability in n/a, published on 7 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-52492 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-52492/ (Markdown: https://insights.sbomify.com/CVE-2025-52492/index.md)","id":"CVE-2025-52492","markdown":"https://insights.sbomify.com/CVE-2025-52492/index.md","name":"CVE-2025-52492","record":{"aliases":["GHSA-h238-7vfv-rhh9"],"analysis":{"component_type":"hardware_firmware","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Paxton10 firmware","requires_auth":"none","summary":"Attackers can extract hard-coded Twilio API credentials from Paxton10 firmware, enabling unauthorized access to the associated Twilio account and services.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2025-52492","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2025-52493"},"packages":[],"prev":{"headline":"Server-side request forgery in CloudTest","id":"CVE-2025-52491"},"products":["n/a"],"published":"2025-07-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-07-08","vendors":["n/a"]},"summary":"Attackers can extract hard-coded Twilio API credentials from Paxton10 firmware, enabling unauthorized access to the associated Twilio account and services.","url":"https://insights.sbomify.com/CVE-2025-52492/"}