{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15123 exists.","fix":"No fix has been published for CVE-2025-15123 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-15123 is a low-severity missing authorization vulnerability in Jeecg Jeecg Boot, published on 28 Dec 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-15123 and fix it if it is affected.\n\nWhat it is: CVE-2025-15123 is a low-severity missing authorization vulnerability in Jeecg Jeecg Boot, published on 28 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15123 exists.\n\nAffected product: Jeecg Jeecg Boot. 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-15123/ (Markdown: https://insights.sbomify.com/CVE-2025-15123/index.md)","id":"CVE-2025-15123","markdown":"https://insights.sbomify.com/CVE-2025-15123/index.md","name":"CVE-2025-15123","record":{"aliases":["GHSA-m84v-87w9-mgjq"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"JeecgBoot low-code platform","requires_auth":"low_privilege","summary":"Remote attackers can bypass authorization controls in JeecgBoot's data rule module, though exploitation requires high complexity.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"jeecg_boot","vendor":"jeecg"}],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/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-863","name":"Incorrect Authorization"},{"id":"CWE-285","name":"Improper Authorization"},{"id":"CWE-266","name":"Incorrect Privilege Assignment"}],"description":"A vulnerability was determined in JeecgBoot up to 3.9.0. This affects an unknown function of the file /sys/sysDepartPermission/datarule/. Executing manipulation can lead to improper authorization. It is possible to launch the attack remotely. The attack requires a high level of complexity. The exploitability is reported as difficult. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.","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":"JeecgBoot datarule improper authorization","id":"CVE-2025-15123","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"jeecg:jeecg_boot","products":["jeecg:jeecg_boot"],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"JeecgBoot list getParameterMap improper authorization","id":"CVE-2025-15124"},"packages":[],"prev":{"headline":"JeecgBoot datarule loadDatarule improper authorization","id":"CVE-2025-15122"},"products":["JeecgBoot"],"published":"2025-12-28","related":[{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2024-40489","kev_date_added":null,"published":"2026-04-01"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2024-43028","kev_date_added":null,"published":"2026-04-01"},{"cvss_score":9.8,"headline":"JeecgBoot SQL Injection vulnerability","id":"CVE-2024-48307","kev_date_added":null,"published":"2024-10-31"},{"cvss_score":9.8,"headline":"Jeecg Boot SQL injection vulnerability","id":"CVE-2023-41542","kev_date_added":null,"published":"2023-12-30"},{"cvss_score":9.8,"headline":"Jeecg Boot SQL Injection","id":"CVE-2023-41543","kev_date_added":null,"published":"2023-12-30"},{"cvss_score":9.8,"headline":"JeecgBoot server-side template injection","id":"CVE-2023-41544","kev_date_added":null,"published":"2023-12-30"},{"cvss_score":9.8,"headline":"SQL injection in jeecgboot","id":"CVE-2023-40989","kev_date_added":null,"published":"2023-09-22"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-29","vendors":["n/a"]},"summary":"Remote attackers can bypass authorization controls in JeecgBoot's data rule module, though exploitation requires high complexity.","url":"https://insights.sbomify.com/CVE-2025-15123/"}