CVE-2025-6699VulnerabilityPublished 26 Jun 2025

CVE-2025-6699: LabRedesCefetRJ WeGIA · Cross Site Scripting

Affects LabRedesCefetRJ WeGIASource CVE Database V5

Mentioned vulnerabilities

CVE-2025-23030

Not known to be exploited · CVSS 5.1 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHublabredescefetrj/WeGIA`pkg:github/labredescefetrj/WeGIA`Other threats	Affected =3.4.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

2) Conduct input validation and output encoding on the server side where possible, even if the vendor has not released a fix, by applying reverse proxies or middleware that sanitize inputs before reaching the application. 3) Educate users and administrators about the risks of clicking on suspicious links and implement Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. 4) Monitor web server logs for unusual requests or payload patterns targeting the vulnerable endpoint. 5) Isolate or restrict access to the affected application to trusted networks until a patch is available. 6) Engage with the vendor or community to track any forthcoming patches or updates. 7) Consider upgrading or migrating to alternative software solutions if feasible to reduce exposure.

Description

A vulnerability classified as problematic has been found in LabRedesCefetRJ WeGIA 3.4.0. This affects an unknown part of the file /html/funcionario/cadastro_funcionario.php of the component Cadastro de Funcionário. The manipulation of the argument Nome/Sobrenome leads to cross site scripting. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. This is a different issue than CVE-2025-23030. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations using LabRedesCefetRJ WeGIA 3.4.0, this vulnerability poses a moderate risk primarily to web application users and administrators. Successful exploitation could lead to session hijacking, unauthorized actions performed under the victim's credentials, or distribution of malicious content, potentially undermining user trust and leading to data leakage or reputational damage. Although the vulnerability does not directly compromise backend systems or data integrity at a high level, it can serve as an entry point for social engineering or further attacks. Organizations in sectors with strict data protection regulations such as GDPR may face compliance risks if user data is exposed. The lack of vendor response and patch availability increases the urgency for organizations to implement compensating controls. The impact is more pronounced in environments where WeGIA is used for managing employee or personnel records, as attackers could leverage the XSS to manipulate or exfiltrate sensitive information indirectly.

Summary

CVE-2025-6699 is a cross-site scripting (XSS) vulnerability identified in version 3.4.0 of the LabRedesCefetRJ WeGIA software, specifically within the 'Cadastro de Funcionário' component located in the /html/funcionario/cadastro_funcionario.php file. The vulnerability arises due to improper sanitization or validation of user-supplied input in the 'Nome' and 'Sobrenome' parameters, which can be manipulated by an attacker to inject malicious scripts. This flaw allows remote attackers to execute arbitrary JavaScript in the context of the victim's browser without requiring authentication, although user interaction is necessary to trigger the payload (e.g., by visiting a crafted URL). The CVSS 4.0 base score is 5.1 (medium severity), reflecting that the attack vector is network-based with low attack complexity, no privileges required, but user interaction is needed. The vulnerability impacts confidentiality and integrity to a limited extent by potentially stealing session cookies, performing actions on behalf of the user, or defacing web content. The vendor was notified early but has not responded or issued a patch, and no known exploits have been observed in the wild yet. This vulnerability is distinct from CVE-2025-23030, indicating multiple security issues in the product. Given the public disclosure and lack of remediation, the risk of exploitation may increase over time.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Jun 2025, 16:05 UTC

Technical details

References

Community reviews

Related threats