{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7305 exists.","fix":"No fix has been published for CVE-2026-7305 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-7305 is a medium-severity server-side request forgery vulnerability in Xuxueli xxl-job, published on 28 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-7305 and fix it if it is affected.\n\nWhat it is: CVE-2026-7305 is a medium-severity server-side request forgery vulnerability in Xuxueli xxl-job, published on 28 Apr 2026. 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-2026-7305 exists.\n\nAffected product: Xuxueli xxl-job. 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-7305/ (Markdown: https://insights.sbomify.com/CVE-2026-7305/index.md)","id":"CVE-2026-7305","markdown":"https://insights.sbomify.com/CVE-2026-7305/index.md","name":"CVE-2026-7305","record":{"aliases":["GHSA-j6qx-2x9m-x936"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"xxl-job scheduling platform","requires_auth":"low_privilege","summary":"An attacker with management access can exploit the trigger endpoint to perform server-side request forgery, though the maintainer disputes the vulnerability's validity.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"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/E:P","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"A weakness has been identified in Xuxueli xxl-job up to 3.3.2. The affected element is the function triggerJob of the file xxl-job-admin/src/main/java/com/xxl/job/admin/service/impl/XxlJobServiceImpl.java of the component trigger Endpoint. This manipulation of the argument addressList causes server-side request forgery. It is possible to initiate the attack remotely. The exploit has been made available to the public and could be used for attacks. There is ongoing doubt regarding the real existence of this vulnerability. The project maintainer explains (translated from Chinese): \"Triggers are manually activated and involve login and access control, thus requiring management.\" The pull request by the researcher got rejected because of that.","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":"Xuxueli xxl-job trigger Endpoint XxlJobServiceImpl.java triggerJob server-side request forgery","id":"CVE-2026-7305","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"Xuxueli xxl-job OpenAPI Endpoint OpenApiController.java hard-coded key","id":"CVE-2026-7306"},"packages":[],"prev":{"headline":"CVE-2026-7304","id":"CVE-2026-7304"},"products":["xxl-job"],"published":"2026-04-28","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-29","vendors":["Xuxueli"]},"summary":"An attacker with management access can exploit the trigger endpoint to perform server-side request forgery, though the maintainer disputes the vulnerability's validity.","url":"https://insights.sbomify.com/CVE-2026-7305/"}