{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-4130 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-4130 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-4130 is a high-severity vulnerability in PAVO Pay, published on 21 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-4130 and fix it if it is affected.\n\nWhat it is: CVE-2025-4130 is a high-severity vulnerability in PAVO Pay, published on 21 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-4130 in the wild and no public exploit code.\n\nAffected product: PAVO Pay. 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-4130/ (Markdown: https://insights.sbomify.com/CVE-2025-4130/index.md)","id":"CVE-2025-4130","markdown":"https://insights.sbomify.com/CVE-2025-4130/index.md","name":"CVE-2025-4130","record":{"aliases":["GHSA-35jm-qwg4-c8wj"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"PAVO Pay","requires_auth":"none","summary":"Attackers can extract sensitive constants from the PAVO Pay executable due to hardcoded credentials, potentially compromising application security.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"TR-CERT","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","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":"Use of Hard-coded Credentials vulnerability in PAVO Inc. PAVO Pay allows Read Sensitive Constants Within an Executable.\n\nThis issue affects PAVO Pay: before 13.05.2025.","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 PAVO Inc.'s PAVO Pay","id":"CVE-2025-4130","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":"GmapsMania \u003c= 1.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode","id":"CVE-2025-4131"},"packages":[],"prev":{"headline":"IDOR in PAVO Inc.'s PAVO Pay","id":"CVE-2025-4129"},"products":["PAVO Pay"],"published":"2025-07-21","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":"2026-06-05","vendors":["PAVO Inc."]},"summary":"Attackers can extract sensitive constants from the PAVO Pay executable due to hardcoded credentials, potentially compromising application security.","url":"https://insights.sbomify.com/CVE-2025-4130/"}