{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-28080 exists.","fix":"No fix has been published for CVE-2022-28080 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-28080 is a high-severity SQL injection vulnerability in n/a, published on 5 May 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-28080 and fix it if it is affected.\n\nWhat it is: CVE-2022-28080 is a high-severity SQL injection vulnerability in n/a, published on 5 May 2022. 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-2022-28080 exists.\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-2022-28080/ (Markdown: https://insights.sbomify.com/CVE-2022-28080/index.md)","id":"CVE-2022-28080","markdown":"https://insights.sbomify.com/CVE-2022-28080/index.md","name":"CVE-2022-28080","record":{"aliases":["GHSA-r54g-jm5f-4gvj"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Event Management System","requires_auth":"low_privilege","summary":"Attackers can exploit SQL injection in the Royal Event Management System to read or modify database contents via the todate parameter.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"event_management_system","vendor":"event_management_system_project"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/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":"Royal Event Management System v1.0 was discovered to contain a SQL injection vulnerability via the todate parameter.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2022-03-30","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":1,"refs":[{"date":"2022-03-30T06:37:48Z","kind":"github_poc","ref":"https://github.com/erengozaydin/Royal-Event-Management-System-todate-SQL-Injection-Authenticated","stars":0,"title":"CVE-2022-28080"},{"date":"2022-05-12","kind":"exploitdb","ref":"50934","stars":null,"title":"Royal Event Management System 1.0 - 'todate' SQL Injection (Authenticated)"},{"date":null,"kind":"nuclei","ref":"http/cves/2022/CVE-2022-28080.yaml","stars":null,"title":"Royal Event - SQL Injection"}],"tier":"weaponised"},"has_fix":null,"headline":"SQL injection in n/a","id":"CVE-2022-28080","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2022-28081"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2022-28079"},"products":["n/a"],"published":"2022-05-05","related":[{"cvss_score":7.3,"headline":"SourceCodester Royale Event Management System userregister.php improper authentication","id":"CVE-2022-1101","kev_date_added":null,"published":"2023-01-07"},{"cvss_score":7.2,"headline":"File upload in n/a","id":"CVE-2022-38323","kev_date_added":null,"published":"2022-09-15"},{"cvss_score":4.3,"headline":"SourceCodester Royale Event Management System companyprofile.php cross site scripting","id":"CVE-2022-1102","kev_date_added":null,"published":"2023-01-07"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers can exploit SQL injection in the Royal Event Management System to read or modify database contents via the todate parameter.","url":"https://insights.sbomify.com/CVE-2022-28080/"}