{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5310 exists.","fix":"No fix has been published for CVE-2026-5310 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-5310 is a low-severity vulnerability in Enter Software Iperius Backup, published on 1 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-5310 and fix it if it is affected.\n\nWhat it is: CVE-2026-5310 is a low-severity vulnerability in Enter Software Iperius Backup, published on 1 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5310 exists.\n\nAffected product: Enter Software Iperius Backup. 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-2026-5310/ (Markdown: https://insights.sbomify.com/CVE-2026-5310/index.md)","id":"CVE-2026-5310","markdown":"https://insights.sbomify.com/CVE-2026-5310/index.md","name":"CVE-2026-5310","record":{"aliases":["GHSA-m24f-g88m-9r7h"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Backup software","requires_auth":"low_privilege","summary":"A local attacker with high complexity can exploit a hard-coded cryptographic key in Iperius Backup to potentially access protected data or bypass security controls.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":2,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"},{"id":"CWE-320","name":null}],"description":"A vulnerability was identified in Enter Software Iperius Backup up to 8.7.2. This impacts an unknown function of the file IperiusAccounts.ini. Such manipulation leads to use of hard-coded cryptographic key\r . The attack must be carried out locally. This attack is characterized by high complexity. The exploitability is said to be difficult. The exploit is publicly available and might be used. Upgrading to version 8.7.4 will fix this issue. It is suggested to upgrade the affected component. The vendor was contacted early, responded in a very professional manner and quickly released a fixed version of the affected product.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Enter Software Iperius Backup IperiusAccounts.ini hard-coded key","id":"CVE-2026-5310","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"D-Link DNS-1550-04 file_center.cgi Webdav_Access_List access control","id":"CVE-2026-5311"},"packages":[],"prev":{"headline":"Authorization Bypass Through User-Controlled Key in GitLab","id":"CVE-2026-5309"},"products":["Iperius Backup"],"published":"2026-04-01","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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-01","vendors":["Enter Software"]},"summary":"A local attacker with high complexity can exploit a hard-coded cryptographic key in Iperius Backup to potentially access protected data or bypass security controls.","url":"https://insights.sbomify.com/CVE-2026-5310/"}