CVE-2025-53525
BaseFortify
Publication date: 2025-07-07
Last updated on: 2025-07-10
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wegia | wegia | to 3.4.3 (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-53525 is a Reflected Cross-Site Scripting (XSS) vulnerability in the WeGIA web application, specifically in the 'profile_familiar.php' endpoint. It occurs because the application does not properly validate or sanitize the 'id_dependente' parameter from the GET request. This allows an attacker to inject malicious scripts that are reflected in the server's response and executed in the victim's browser, potentially leading to unauthorized actions or data theft. [1]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized user actions, theft of sensitive data, account compromise through cookie manipulation, execution of malicious code in the user's browser, damage to the business's reputation, and user misdirection. It requires user interaction but can be triggered remotely without any privileges. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'profile_familiar.php' endpoint with the 'id_dependente' GET parameter for reflected script injection. A simple test command using curl would be: curl -G --data-urlencode "id_dependente=<script>alert(1)</script>" http://your-wegia-domain/html/atendido/profile_familiar.php and observing if the script is reflected in the response. If the script appears unescaped in the response, the system is vulnerable. Additionally, web vulnerability scanners that test for reflected XSS on GET parameters can be used. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the WeGIA application to version 3.4.3 or later, where the vulnerability is fixed. The fix involves sanitizing the 'id_dependente' parameter using PHP's filter_input with FILTER_SANITIZE_NUMBER_INT, validating input strictly, terminating execution with an HTTP 400 error on invalid input, and avoiding direct output of unsanitized user input in HTML and JavaScript contexts. If updating is not immediately possible, manually applying similar input sanitization and validation measures to the 'profile_familiar.php' endpoint can reduce risk. [2]