{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65032 exists.","fix":"No fix has been published for CVE-2025-65032 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-65032 is a medium-severity missing authorization vulnerability in lukevella rallly, published on 19 Nov 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-65032 and fix it if it is affected.\n\nWhat it is: CVE-2025-65032 is a medium-severity missing authorization vulnerability in lukevella rallly, published on 19 Nov 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-65032 exists.\n\nAffected product: lukevella rallly. 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-65032/ (Markdown: https://insights.sbomify.com/CVE-2025-65032/index.md)","id":"CVE-2025-65032","markdown":"https://insights.sbomify.com/CVE-2025-65032/index.md","name":"CVE-2025-65032","record":{"aliases":["GHSA-q9m7-chfx-43xw"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Scheduling collaboration tool","requires_auth":"low_privilege","summary":"Authenticated users can modify other participants' display names in polls by manipulating the participantId parameter, violating data integrity.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"rallly","vendor":"rallly"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"Rallly is an open-source scheduling and collaboration tool. Prior to version 4.5.4, an Insecure Direct Object Reference (IDOR) vulnerability allows any authenticated user to change the display names of other participants in polls without being an admin or the poll owner. By manipulating the participantId parameter in a rename request, an attacker can modify another user’s name, violating data integrity and potentially causing confusion or impersonation attacks. This issue has been patched in version 4.5.4.","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":"Rallly Has an IDOR Vulnerability in Participant Rename Function Allows Unauthorized Modification of Other Users’ Names","id":"CVE-2025-65032","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Rallly Broken Authorization: Any User Can Pause or Resume Any Poll via Poll ID Manipulation","id":"CVE-2025-65033"},"packages":[],"prev":{"headline":"Rallly Improper Authorization in Comment Endpoint Allows User Impersonation","id":"CVE-2025-65031"},"products":["rallly"],"published":"2025-11-19","related":[{"cvss_score":9.8,"headline":"Rallly Insufficient Password Login Token Entropy Leads to Account Takeover","id":"CVE-2025-47781","kev_date_added":null,"published":"2025-05-14"},{"cvss_score":9.1,"headline":"Rallly Has Unauthorized Poll Finalization via Insecure Direct Object Reference (IDOR)","id":"CVE-2025-65021","kev_date_added":null,"published":"2025-11-19"},{"cvss_score":8.1,"headline":"Rallly Has an IDOR Vulnerability in Participant Deletion Endpoint Allows Unauthorized Removal of Poll Participants","id":"CVE-2025-65029","kev_date_added":null,"published":"2025-11-19"},{"cvss_score":8.1,"headline":"Rallly Broken Authorization: Any User Can Pause or Resume Any Poll via Poll ID Manipulation","id":"CVE-2025-65033","kev_date_added":null,"published":"2025-11-19"},{"cvss_score":8.1,"headline":"Rallly Improper Authorization Allows Reopening of Any Finalized Poll via Public pollId","id":"CVE-2025-65034","kev_date_added":null,"published":"2025-11-19"},{"cvss_score":7.1,"headline":"Rallly Information Disclosure Vulnerability in Participant API Leaks Names and Emails Despite Pro Privacy Settings","id":"CVE-2025-66027","kev_date_added":null,"published":"2025-11-29"},{"cvss_score":7.1,"headline":"Rallly Improper Authorization in Comment Deletion Endpoint Allows Unauthorized Comment Removal","id":"CVE-2025-65030","kev_date_added":null,"published":"2025-11-19"}],"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-11-19","vendors":["lukevella"]},"summary":"Authenticated users can modify other participants' display names in polls by manipulating the participantId parameter, violating data integrity.","url":"https://insights.sbomify.com/CVE-2025-65032/"}