Flexmls IDX Plugin up to 3.14.27 on WordPress deserialization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Flexmls IDX Plugin up to 3.14.27 on WordPress. It has been classified as critical. This affects an unknown function. The manipulation leads to deserialization. This vulnerability is uniquely identified as CVE-2025-26900. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability, which was classified as critical, has been found in Flexmls IDX Plugin up to 3.14.27 on WordPress. This issue affects an unknown code block. 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. The summary by CVE is:
Deserialization of Untrusted Data vulnerability in flexmls Flexmls® IDX allows Object Injection. This issue affects Flexmls® IDX: from n/a through 3.14.27.
The weakness was disclosed by Phat Rio. The advisory is shared at patchstack.com. The identification of this vulnerability is CVE-2025-26900 since 02/17/2025. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/25/2025).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
- 3.14.0
- 3.14.1
- 3.14.2
- 3.14.3
- 3.14.4
- 3.14.5
- 3.14.6
- 3.14.7
- 3.14.8
- 3.14.9
- 3.14.10
- 3.14.11
- 3.14.12
- 3.14.13
- 3.14.14
- 3.14.15
- 3.14.16
- 3.14.17
- 3.14.18
- 3.14.19
- 3.14.20
- 3.14.21
- 3.14.22
- 3.14.23
- 3.14.24
- 3.14.25
- 3.14.26
- 3.14.27
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 9.8
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
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
02/17/2025 🔍02/25/2025 🔍
02/25/2025 🔍
02/25/2025 🔍
Sources
Advisory: patchstack.comResearcher: Phat Rio
Status: Not defined
CVE: CVE-2025-26900 (🔍)
GCVE (CVE): GCVE-0-2025-26900
GCVE (VulDB): GCVE-100-296777
Entry
Created: 02/25/2025 15:45Changes: 02/25/2025 15:45 (63)
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.