{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-5698 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-5698 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-5698 is a medium-severity SQL injection vulnerability in Brilliance Golden Link Secondary System, published on 5 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-5698 and fix it if it is affected.\n\nWhat it is: CVE-2025-5698 is a medium-severity SQL injection vulnerability in Brilliance Golden Link Secondary System, published on 5 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-5698 in the wild and no public exploit code.\n\nAffected product: Brilliance Golden Link Secondary System. 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-5698/ (Markdown: https://insights.sbomify.com/CVE-2025-5698/index.md)","id":"CVE-2025-5698","markdown":"https://insights.sbomify.com/CVE-2025-5698/index.md","name":"CVE-2025-5698","record":{"aliases":["GHSA-wmmm-6p9c-hggv"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Brilliance Golden Link","requires_auth":"low_privilege","summary":"Remote attackers can exploit SQL injection in the logSelect.htm file to read or modify database contents in Brilliance Golden Link Secondary System.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"golden_link_secondary_system","vendor":"brilliance"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"},{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"A vulnerability, which was classified as critical, was found in Brilliance Golden Link Secondary System up to 20250424. Affected is an unknown function of the file /sysframework/logSelect.htm. The manipulation of the argument nodename leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.","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":"Brilliance Golden Link Secondary System logSelect.htm sql injection","id":"CVE-2025-5698","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Developer Formatter \u003c= 2015.0.2.1 - Authenticated (Administrator+) Stored Cross-Site Scripting via Custom CSS","id":"CVE-2025-5699"},"packages":[],"prev":{"headline":"Brilliance Golden Link Secondary System tcCustDeferPosiQuery.htm sql injection","id":"CVE-2025-5697"},"products":["Golden Link Secondary System"],"published":"2025-06-05","related":[{"cvss_score":5.3,"headline":"Brilliance Golden Link Secondary System rentTakeInfoPage.htm sql injection","id":"CVE-2025-6276","kev_date_added":null,"published":"2025-06-19"},{"cvss_score":5.3,"headline":"Brilliance Golden Link Secondary System custTakeInfoPage.htm sql injection","id":"CVE-2025-6277","kev_date_added":null,"published":"2025-06-19"},{"cvss_score":5.3,"headline":"Brilliance Golden Link Secondary System rentChangeCheckInfoPage.htm sql injection","id":"CVE-2025-5696","kev_date_added":null,"published":"2025-06-05"},{"cvss_score":5.3,"headline":"Brilliance Golden Link Secondary System tcCustDeferPosiQuery.htm sql injection","id":"CVE-2025-5697","kev_date_added":null,"published":"2025-06-05"},{"cvss_score":5.3,"headline":"Brilliance Golden Link Secondary System tcEntrFlowSelect.htm sql injection","id":"CVE-2025-4352","kev_date_added":null,"published":"2025-05-06"},{"cvss_score":5.3,"headline":"Brilliance Golden Link Secondary System queryTsDictionaryType.htm sql injection","id":"CVE-2025-4353","kev_date_added":null,"published":"2025-05-06"}],"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-09","vendors":["Brilliance"]},"summary":"Remote attackers can exploit SQL injection in the logSelect.htm file to read or modify database contents in Brilliance Golden Link Secondary System.","url":"https://insights.sbomify.com/CVE-2025-5698/"}