Exponent CMS up to 2.5.x purchaseOrderController.php input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in Exponent CMS up to 2.5.x. Impacted is an unknown function of the file purchaseOrderController.php. Such manipulation leads to input validation. This vulnerability is listed as CVE-2016-9025. There is no available exploit. Upgrading the affected component is recommended.
Details
A vulnerability was found in Exponent CMS up to 2.5.x (Content Management System) and classified as critical. Affected by this issue is an unknown code block of the file purchaseOrderController.php. The manipulation with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. Impacted is confidentiality, integrity, and availability.
The weakness was presented 12/31/2020 as a8efd9ca71fc9b8b843ad0910d435d237482ee31. The advisory is available at github.com. This vulnerability is handled as CVE-2016-9025. Technical details are known, but there is no available exploit.
By approaching the search of inurl:purchaseOrderController.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 2.6.0 eliminates this vulnerability. Applying a patch 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 best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
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: Input validationCWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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: CMS 2.6.0
Patch: github.com
Timeline
12/31/2020 🔍12/31/2020 🔍
12/31/2020 🔍
Sources
Advisory: a8efd9ca71fc9b8b843ad0910d435d237482ee31Status: Confirmed
CVE: CVE-2016-9025 (🔍)
GCVE (CVE): GCVE-0-2016-9025
GCVE (VulDB): GCVE-100-167018
Entry
Created: 12/31/2020 08:41Changes: 12/31/2020 08:41 (41)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.