CVE-2025-6698
BaseFortify
Publication date: 2025-06-26
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wegia | wegia | 3.4.0 |
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. |
| CWE-94 | The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-6698 is a Stored Cross-Site Scripting (XSS) vulnerability in LabRedesCefetRJ WeGIA version 3.4.0. It occurs in the output type registration feature where an attacker can inject malicious JavaScript code into the 'output type name' field. This input is stored in the database without proper validation or sanitization, causing the malicious script to execute in the browser of any user who accesses the related product registration page. This can lead to session hijacking, unauthorized redirects, or other client-side attacks. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to execute malicious scripts in your users' browsers when they access the affected page. This can result in session hijacking, unauthorized redirects, and compromise of application integrity and user security. Since the attack can be launched remotely and the exploit is publicly available, it poses a real risk to the confidentiality and integrity of your users' interactions with the application. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by attempting to inject a test script payload into the output type name field in the WeGIA platform and observing if it executes when the related page loads. Specifically, log into the WeGIA platform, navigate to Material e Patrimonio > Entrada > Registrar Saida, then on /html/matPat/cadastro_saida.php click the '+' button under the 'Tipo' tab, and submit a new output type with a payload such as <script>alert('Poc VulDB')</script> in the name field on /html/matPat/adicionar_tipoSaida.php. If the alert executes when loading /html/matPat/cadastro_saida.php, the vulnerability is present. Additionally, attackers can locate vulnerable instances using Google dorking with queries like: inurl:html/matPat/adicionar_tipoSaida.php [1, 2]
What immediate steps should I take to mitigate this vulnerability?
No known countermeasures or mitigations have been published for this vulnerability. The suggested immediate step is to replace the affected component or product with an alternative that does not have this vulnerability. Additionally, avoid using the vulnerable functionality until a patch or fix is available, and restrict access to the affected pages to trusted users only. [2]