Intelliants Subrion CMS up to 4.1.5 /front/actions.php $_POST sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Intelliants Subrion CMS up to 4.1.5. It has been classified as critical. Affected is an unknown function of the file /front/actions.php. Performing a manipulation of the argument $_POST results in sql injection. This vulnerability was named CVE-2017-11445. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as critical, was found in Intelliants Subrion CMS up to 4.1.5 (Content Management System). This affects an unknown code block of the file /front/actions.php. The manipulation of the argument $_POST with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Subrion CMS before 4.1.6 has a SQL injection vulnerability in /front/actions.php via the $_POST array.
The bug was discovered 07/02/2017. The weakness was presented 07/19/2017 (GitHub Repository). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2017-11445 since 07/19/2017. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 17 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:front/actions.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 4.1.6 eliminates this vulnerability.
See VDB-103772 for similar entry. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.1
VulDB Base Score: 7.3
VulDB Temp Score: 6.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD 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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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: Subrion CMS 4.1.6
Timeline
07/02/2017 🔍07/19/2017 🔍
07/19/2017 🔍
07/19/2017 🔍
07/19/2017 🔍
12/13/2022 🔍
Sources
Advisory: 480Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-11445 (🔍)
GCVE (CVE): GCVE-0-2017-11445
GCVE (VulDB): GCVE-100-103773
See also: 🔍
Entry
Created: 07/19/2017 23:11Updated: 12/13/2022 09:23
Changes: 07/19/2017 23:11 (61), 10/27/2019 10:25 (2), 12/13/2022 09:23 (4)
Complete: 🔍
Cache ID: 216:691:103
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.