CVE-2025-55287
BaseFortify
Publication date: 2025-08-18
Last updated on: 2025-09-03
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| kreaweb | genealogy | to 4.4.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-55287 is a Stored Cross-Site Scripting (XSS) vulnerability in the Genealogy PHP application versions prior to 4.4.0. Authenticated attackers can inject malicious JavaScript code that is stored by the application and later executed in other users' browsers. This happens because the application does not properly escape or sanitize user input, allowing the malicious script to persist and run when viewed by other users. [1]
How can this vulnerability impact me? :
This vulnerability can lead to session hijacking, where attackers steal user session tokens to impersonate users. It can also cause data theft by exfiltrating sensitive information, and UI manipulation attacks that alter the appearance or behavior of the application for other users. Overall, it compromises confidentiality, integrity, and availability of user data and application functionality. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves identifying stored XSS payloads injected by authenticated users. Since it is a Stored Cross-Site Scripting vulnerability, you can look for suspicious JavaScript code in user input fields or stored content rendered in other users' browsers. Manual testing by logging in as an authenticated user and attempting to inject typical XSS payloads (e.g., <script>alert(1)</script>) into input fields can help detect the issue. Additionally, web application security scanners that support authenticated scans and detect stored XSS can be used. There are no specific commands provided in the resources. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include upgrading the Genealogy application to version 4.4.0 or later, which contains the fix for this vulnerability. If upgrading immediately is not possible, it is recommended to escape or sanitize all user-supplied content before rendering it in the application to prevent malicious JavaScript execution. Additionally, review and secure file storage configurations to prevent unauthorized access to sensitive files. [1]