b1gMail up to 7.4.1-pl1 Admin Page src/admin/users.php query/q deserialization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in b1gMail up to 7.4.1-pl1. It has been rated as problematic. This issue affects some unknown processing of the file src/admin/users.php of the component Admin Page. This manipulation of the argument query/q causes deserialization. The identification of this vulnerability is CVE-2025-1741. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is advised. The vendor acted highly professional and even fixed this issue in the discontinued commercial edition as b1gMail 7.4.0-pl3.
Details
A vulnerability classified as problematic was found in b1gMail up to 7.4.1-pl1. Affected by this vulnerability is an unknown function of the file src/admin/users.php of the component Admin Page. The manipulation of the argument query/q with an unknown input leads to a deserialization vulnerability. The CWE definition for the vulnerability is CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. As an impact it is known to affect confidentiality, integrity, and availability.
The advisory is shared at gist.github.com. This vulnerability is known as CVE-2025-1741. The exploitation appears to be easy. The attack can be launched remotely. Additional levels of successful authentication are needed for exploitation. Technical details are known, but no exploit is available.
The vendor acted highly professional and even fixed this issue in the discontinued commercial edition as b1gMail 7.4.0-pl3. By approaching the search of inurl:src/admin/users.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 7.4.1-pl2 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 4816c8b748f6a5b965c8994e2cf10861bf6e68aa is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.7VulDB Meta Temp Score: 4.5
VulDB Base Score: 4.7
VulDB Temp Score: 4.5
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: DeserializationCWE: CWE-502 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
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: b1gMail 7.4.1-pl2
Patch: 4816c8b748f6a5b965c8994e2cf10861bf6e68aa
Timeline
02/23/2025 🔍02/27/2025 🔍
02/27/2025 🔍
02/27/2025 🔍
Sources
Advisory: gist.github.comStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2025-1741 (🔍)
GCVE (CVE): GCVE-0-2025-1741
GCVE (VulDB): GCVE-100-297829
Entry
Created: 02/27/2025 09:52Changes: 02/27/2025 09:52 (60)
Complete: 🔍
Submitter: mcdruid
Cache ID: 216::103
Submit
Accepted
- Submit #505838: b1gMail-OSS b1gMail 7.4.1-pl1 Deserialization (by mcdruid)
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.