CVE-2025-65031
BaseFortify
Publication date: 2025-11-19
Last updated on: 2025-11-25
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| rallly | rallly | to 4.5.4 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-639 | The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. |
| CWE-285 | The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in Rallly versions prior to 4.5.4 is an improper authorization flaw in the comment creation endpoint. Authenticated users can manipulate the authorName field in the API request to impersonate any other user, including privileged users like administrators. This allows attackers to post comments under arbitrary usernames, potentially misleading other users.
How can this vulnerability impact me? :
The vulnerability can impact you by allowing attackers to impersonate other users, including administrators, through posted comments. This can mislead users, facilitate phishing or social engineering attacks, and undermine trust in the platform's communication.
What immediate steps should I take to mitigate this vulnerability?
Upgrade Rallly to version 4.5.4 or later, where the improper authorization flaw in the comment creation endpoint has been patched. Until the upgrade is applied, restrict authenticated user access to the comment creation API and monitor for suspicious comment activity that may indicate impersonation attempts.