Select-mes Zermatt Plugin up to 1.6.1 on WordPress deserialization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $0-$5k | 0.87 |
Summary
A vulnerability categorized as problematic has been discovered in Select-mes Zermatt Plugin up to 1.6.1 on WordPress. Affected is an unknown function. Such manipulation leads to deserialization. This vulnerability is documented as CVE-2026-39545. The attack can be executed remotely. There is not any exploit available.
Details
A vulnerability was found in Select-mes Zermatt Plugin up to 1.6.1 on WordPress and classified as problematic. Affected by this issue is an unknown functionality. The manipulation with an unknown input leads to a deserialization vulnerability. Using CWE to declare the problem leads to CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. Impacted is confidentiality, integrity, and availability. CVE summarizes:
Unauthenticated PHP Object Injection in Zermatt <= 1.6.1 versions.
The weakness was released by Denver Jackson. The advisory is shared for download at patchstack.com. This vulnerability is handled as CVE-2026-39545 since 04/07/2026. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 06/17/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.7
VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 8.1
CNA Vector (Patchstack): 🔒
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
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
04/07/2026 CVE reserved06/17/2026 Advisory disclosed
06/17/2026 VulDB entry created
06/17/2026 VulDB entry last update
Sources
Advisory: patchstack.comResearcher: Denver Jackson
Status: Not defined
CVE: CVE-2026-39545 (🔒)
GCVE (CVE): GCVE-0-2026-39545
GCVE (VulDB): GCVE-100-371876
Entry
Created: 06/17/2026 13:34Changes: 06/17/2026 13:34 (63)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.