{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-47730 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-47730 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-47730 is a medium-severity vulnerability in TeleMessage archiving backend, published on 8 May 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-47730 and fix it if it is affected.\n\nWhat it is: CVE-2025-47730 is a medium-severity vulnerability in TeleMessage archiving backend, published on 8 May 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-47730 in the wild and no public exploit code.\n\nAffected product: TeleMessage archiving backend. 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-47730/ (Markdown: https://insights.sbomify.com/CVE-2025-47730/index.md)","id":"CVE-2025-47730","markdown":"https://insights.sbomify.com/CVE-2025-47730/index.md","name":"CVE-2025-47730","record":{"aliases":["GHSA-9qc4-m2hc-5vc5"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"TeleMessage archiving backend","requires_auth":"none","summary":"Hardcoded credentials in the TeleMessage archiving backend allow attackers to obtain authentication tokens and access user data.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"telemessage","vendor":"smarsh"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"The TeleMessage archiving backend through 2025-05-05 accepts API calls (to request an authentication token) from the TM SGNL (aka Archive Signal) app with the credentials of logfile for the user and enRR8UVVywXYbFkqU#QDPRkO for the password.","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 archiving backend","id":"CVE-2025-47730","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Microsoft Dataverse Remote Code Execution Vulnerability","id":"CVE-2025-47732"},"packages":[],"prev":{"headline":"TeleMessage TM SGNL Hidden Functionality","id":"CVE-2025-47729"},"products":["archiving backend"],"published":"2025-05-08","related":[{"cvss_score":5.3,"headline":"TeleMessage TM SGNL Initialization of a Resource with an Insecure Default","id":"CVE-2025-48927","kev_date_added":"2025-07-01","published":"2025-05-28"},{"cvss_score":4,"headline":"TeleMessage TM SGNL Exposure of Core Dump File to an Unauthorized Control Sphere","id":"CVE-2025-48928","kev_date_added":"2025-07-01","published":"2025-05-28"},{"cvss_score":4.3,"headline":"Weak cryptography in service","id":"CVE-2025-48925","kev_date_added":null,"published":"2025-05-28"},{"cvss_score":4.3,"headline":"Information disclosure in service","id":"CVE-2025-48926","kev_date_added":null,"published":"2025-05-28"},{"cvss_score":4,"headline":"Auth bypass in service","id":"CVE-2025-48929","kev_date_added":null,"published":"2025-05-28"},{"cvss_score":3.2,"headline":"Weak cryptography in service","id":"CVE-2025-48931","kev_date_added":null,"published":"2025-05-28"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-08","vendors":["TeleMessage"]},"summary":"Hardcoded credentials in the TeleMessage archiving backend allow attackers to obtain authentication tokens and access user data.","url":"https://insights.sbomify.com/CVE-2025-47730/"}