suitenumerique messages 0.2.0 ThreadAccess serializers.py ThreadAccessSerializer improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in suitenumerique messages 0.2.0. Impacted is the function ThreadAccessSerializer of the file src/backend/core/api/serializers.py of the component ThreadAccess. This manipulation causes improper authentication.
This vulnerability is tracked as CVE-2026-3739. The attack is possible to be carried out remotely. Moreover, an exploit is present.
It is suggested to upgrade the affected component.
Details
A vulnerability has been found in suitenumerique messages 0.2.0 and classified as critical. Affected by this vulnerability is the function ThreadAccessSerializer of the file src/backend/core/api/serializers.py of the component ThreadAccess. The manipulation with an unknown input leads to a improper authentication vulnerability. The CWE definition for the vulnerability is CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. As an impact it is known to affect confidentiality, integrity, and availability.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-3739. The exploitation appears to be easy. The attack can be launched remotely. Technical details and also a public exploit are known.
It is possible to download the exploit at github.com. It is declared as proof-of-concept.
Upgrading to version 0.3.0 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch d7729f4b885449f6dee3faf8b5f2a05769fb3d6e 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.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-10242). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
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: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.3
CNA Vector: 🔒
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: Improper authenticationCWE: CWE-287
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
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: messages 0.3.0
Patch: d7729f4b885449f6dee3faf8b5f2a05769fb3d6e
Timeline
03/07/2026 Advisory disclosed03/07/2026 VulDB entry created
03/08/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-7476-6crq-4cw9
Status: Confirmed
Confirmation: 🔒
CVE: CVE-2026-3739 (🔒)
GCVE (CVE): GCVE-0-2026-3739
GCVE (VulDB): GCVE-100-349717
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/07/2026 21:12Updated: 03/08/2026 19:48
Changes: 03/07/2026 21:12 (63), 03/08/2026 18:40 (1), 03/08/2026 19:48 (30)
Complete: 🔍
Submitter: djnn
Cache ID: 216::103
Submit
Accepted
- Submit #767329: La Suite Numerique messages 0.2.0 IDOR (by djnn)
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.