{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-43925 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-43925 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-43925 is a medium-severity vulnerability in n/a, published on 3 Jun 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-43925 and fix it if it is affected.\n\nWhat it is: CVE-2025-43925 is a medium-severity vulnerability in n/a, published on 3 Jun 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-43925 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-43925/ (Markdown: https://insights.sbomify.com/CVE-2025-43925/index.md)","id":"CVE-2025-43925","markdown":"https://insights.sbomify.com/CVE-2025-43925/index.md","name":"CVE-2025-43925","record":{"aliases":["GHSA-3jrw-q59w-mpr2"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Unicom Focal Point","requires_auth":"low_privilege","summary":"Attackers can decrypt the database using a hardcoded key to access cleartext data in Unicom Focal Point.","user_interaction":"required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"focal_point","vendor":"unicomsi"}],"cvss":{"score":4.6,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-326","name":"Inadequate Encryption Strength"}],"description":"An issue was discovered in Unicom Focal Point 7.6.1. The database is encrypted with a hardcoded key, making it easier to recover the cleartext data.","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-43925","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":"Cross-site scripting in n/a","id":"CVE-2025-43926"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-43924"},"products":["n/a"],"published":"2025-06-03","related":[{"cvss_score":6.5,"headline":"SQL injection in n/a","id":"CVE-2025-43923","kev_date_added":null,"published":"2025-06-03"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2025-43924","kev_date_added":null,"published":"2025-06-03"}],"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-06-03","vendors":["n/a"]},"summary":"Attackers can decrypt the database using a hardcoded key to access cleartext data in Unicom Focal Point.","url":"https://insights.sbomify.com/CVE-2025-43925/"}