{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-15849 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-15849 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-15849 is a high-severity SQL injection vulnerability in n/a, published on 30 Sep 2020. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-15849 and fix it if it is affected.\n\nWhat it is: CVE-2020-15849 is a high-severity SQL injection vulnerability in n/a, published on 30 Sep 2020. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-15849 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2020-15849/ (Markdown: https://insights.sbomify.com/CVE-2020-15849/index.md)","id":"CVE-2020-15849","markdown":"https://insights.sbomify.com/CVE-2020-15849/index.md","name":"CVE-2020-15849","record":{"aliases":["GHSA-2wmr-35cq-3r7p"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Re:Desk helpdesk","requires_auth":"high_privilege","summary":"An authenticated admin can exploit SQL injection to read sensitive data, modify password tokens, and execute arbitrary PHP code via framework features.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"re\\","vendor":"re-desk"}],"cvss":{"score":7.2,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"Re:Desk 2.3 has a blind authenticated SQL injection vulnerability in the SettingsController class, in the actionEmailTemplates() method. A malicious actor with access to an administrative account could abuse this vulnerability to recover sensitive data from the application's database, allowing for authorization bypass and taking over additional accounts by means of modifying password-reset tokens stored in the database. Remote command execution is also possible by leveraging this to abuse the Yii framework's bizRule functionality, allowing for arbitrary PHP code to be executed by the application. Remote command execution is also possible by using this together with a separate insecure file upload vulnerability (CVE-2020-15488).","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":"SQL injection in n/a","id":"CVE-2020-15849","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2020-15850"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2020-15843"},"products":["n/a"],"published":"2020-09-30","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2020-15487","kev_date_added":null,"published":"2020-09-30"},{"cvss_score":7.5,"headline":"Re:Desk 2.3 allows insecure file upload.","id":"CVE-2020-15488","kev_date_added":null,"published":"2020-09-30"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"An authenticated admin can exploit SQL injection to read sensitive data, modify password tokens, and execute arbitrary PHP code via framework features.","url":"https://insights.sbomify.com/CVE-2020-15849/"}