Relaticle up to 3.10.0 Import Wizard MappingStep.php mapToField target authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00+ |
Summary
A vulnerability was found in Relaticle up to 3.10.0. It has been classified as critical. This impacts the function mapToField of the file packages/ImportWizard/src/Livewire/Steps/MappingStep.php of the component Import Wizard. Performing a manipulation of the argument Target results in authorization.
This vulnerability is reported as CVE-2026-132137. The attack is possible to be carried out remotely. Moreover, an exploit is present.
The vendor was contacted early about this disclosure.
Details
A vulnerability, which was classified as critical, was found in Relaticle up to 3.10.0. This affects the function mapToField of the file packages/ImportWizard/src/Livewire/Steps/MappingStep.php of the component Import Wizard. The manipulation of the argument target with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. This is going to have an impact on confidentiality, integrity, and availability.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-132137. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details and a public exploit are known.
The exploit is shared for download at github.com. It is declared as proof-of-concept. The vendor was contacted early about this disclosure. By approaching the search of inurl:packages/ImportWizard/src/Livewire/Steps/MappingStep.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
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: AuthorizationCWE: CWE-639 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Google Hack: 🔒
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: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
11/18/2026 Advisory disclosed11/18/2026 VulDB entry created
11/18/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
CNA: VulDB
CVE: CVE-2026-132137 (🔒)
GCVE (CVE): GCVE-0-2026-132137
GCVE (VulDB): GCVE-100-439437
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 11/18/2026 14:09Changes: 11/18/2026 14:09 (57)
Complete: 🔍
Submitter: bobtao666
Cache ID: 216::103
Submit
Accepted
- Submit #958679: Relaticle <=3.5.6 IDOR (by bobtao666)
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.