GPP-Woo GPP-burgerportaal up to 2.0.2/3.0.1/4.0.0 private personal information
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in GPP-Woo GPP-burgerportaal up to 2.0.2/3.0.1/4.0.0. It has been rated as problematic. Affected by this issue is some unknown functionality. This manipulation causes private personal information. This vulnerability appears as CVE-2025-62362. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is advised.
Details
A vulnerability has been found in GPP-Woo GPP-burgerportaal up to 2.0.2/3.0.1/4.0.0 and classified as problematic. Affected by this vulnerability is an unknown function. The manipulation with an unknown input leads to a private personal information vulnerability. The CWE definition for the vulnerability is CWE-359. The product does not properly prevent a person's private, personal information from being accessed by actors who either (1) are not explicitly authorized to access the information or (2) do not have the implicit consent of the person about whom the information is collected. As an impact it is known to affect confidentiality. The summary by CVE is:
gpp-burgerportaal is a Dutch government citizen portal application. In versions before 2.0.3, 3.0.2, and 4.0.1, the name and email address of employees who publish content are exposed in network responses and can be discovered by viewing the browser's developer tools network tab. This information disclosure may violate employee privacy expectations and could be used for targeted attacks or unwanted contact. This issue has been patched in versions 2.0.3, 3.0.2, and 4.0.1. No known workarounds exist.
The advisory is shared at github.com. This vulnerability is known as CVE-2025-62362 since 10/10/2025. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1589 for this issue.
Upgrading to version 2.0.3, 3.0.2 or 4.0.1 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Private personal informationCWE: CWE-359
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: GPP-burgerportaal 2.0.3/3.0.2/4.0.1
Timeline
10/10/2025 CVE reserved10/14/2025 Advisory disclosed
10/14/2025 VulDB entry created
10/14/2025 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-pgg6-2865-2788
Status: Confirmed
CVE: CVE-2025-62362 (🔒)
GCVE (CVE): GCVE-0-2025-62362
GCVE (VulDB): GCVE-100-328153
Entry
Created: 10/14/2025 08:07Changes: 10/14/2025 08:07 (66)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.