{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34455 exists.","fix":"No fix has been published for CVE-2026-34455 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-34455 is a high-severity SQL injection vulnerability in HiEventsDev Hi.Events, published on 1 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-34455 and fix it if it is affected.\n\nWhat it is: CVE-2026-34455 is a high-severity SQL injection vulnerability in HiEventsDev Hi.Events, published on 1 Apr 2026. 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-2026-34455 exists.\n\nAffected product: HiEventsDev Hi.Events. 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-34455/ (Markdown: https://insights.sbomify.com/CVE-2026-34455/index.md)","id":"CVE-2026-34455","markdown":"https://insights.sbomify.com/CVE-2026-34455/index.md","name":"CVE-2026-34455","record":{"aliases":["GHSA-2qcp-24fh-fx6p"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Event management platform","requires_auth":"none","summary":"Attackers can execute arbitrary SQL commands via the sort_by parameter in Hi.Events, potentially reading or modifying database contents.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"hi.events","vendor":"hi.events"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"Hi.Events is an open-source event management and ticket selling platform. From version 0.8.0-beta.1 to before version 1.7.1-beta, multiple repository classes pass the user-supplied sort_by query parameter directly to Eloquent's orderBy() without validation, enabling SQL injection. The application uses PostgreSQL which supports stacked queries. This issue has been patched in version 1.7.1-beta.","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":"Hi.Events: SQL Injection via Unvalidated sort_by Query Parameter in Multiple Repository Classes","id":"CVE-2026-34455","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Reviactyl: OAuth account takeover via auto-linking","id":"CVE-2026-34456"},"packages":[],"prev":{"headline":"OAuth2 Proxy: Session cookie not cleared when rendering sign-in page","id":"CVE-2026-34454"},"products":["Hi.Events"],"published":"2026-04-01","related":[],"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":"2026-04-02","vendors":["HiEventsDev"]},"summary":"Attackers can execute arbitrary SQL commands via the sort_by parameter in Hi.Events, potentially reading or modifying database contents.","url":"https://insights.sbomify.com/CVE-2026-34455/"}