{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-4543 exists.","fix":"No fix has been published for CVE-2025-4543 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-4543 is a medium-severity SQL injection vulnerability in LyLme Spage, published on 11 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-4543 and fix it if it is affected.\n\nWhat it is: CVE-2025-4543 is a medium-severity SQL injection vulnerability in LyLme Spage, published on 11 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-4543 exists.\n\nAffected product: LyLme Spage. 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-4543/ (Markdown: https://insights.sbomify.com/CVE-2025-4543/index.md)","id":"CVE-2025-4543","markdown":"https://insights.sbomify.com/CVE-2025-4543/index.md","name":"CVE-2025-4543","record":{"aliases":["GHSA-wcwc-445x-wf23"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"LyLme Spage CMS","requires_auth":"none","summary":"Remote attackers can exploit SQL injection in the sort parameter of ajax_link.php to read or modify database contents.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"lylme_spage","vendor":"lylme"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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 LyLme Spage 2.1. This affects an unknown part of the file lylme_spage/blob/master/admin/ajax_link.php. The manipulation of the argument sort leads to sql injection. It is possible to initiate 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":"weaponised"},"has_fix":false,"headline":"LyLme Spage ajax_link.php sql injection","id":"CVE-2025-4543","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":"D-Link DI-8100 jhttpd ddos.asp stack-based overflow","id":"CVE-2025-4544"},"packages":[],"prev":{"headline":"Freeebird Hotel 酒店管理系统 API SessionInterceptor.java cross-domain policy","id":"CVE-2025-4542"},"products":["Spage"],"published":"2025-05-11","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2024-48176","kev_date_added":null,"published":"2024-11-05"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-48356","kev_date_added":null,"published":"2024-10-28"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-48357","kev_date_added":null,"published":"2024-10-28"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2024-34982","kev_date_added":null,"published":"2024-05-17"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2023-45951","kev_date_added":null,"published":"2023-10-17"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2023-45952","kev_date_added":null,"published":"2023-10-17"},{"cvss_score":9.1,"headline":"Server-side request forgery in n/a","id":"CVE-2024-36675","kev_date_added":null,"published":"2024-06-04"}],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-12","vendors":["LyLme"]},"summary":"Remote attackers can exploit SQL injection in the sort parameter of ajax_link.php to read or modify database contents.","url":"https://insights.sbomify.com/CVE-2025-4543/"}