SPIP up to 3.1.10/3.2.4 ecrire/inc/meta.php authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in SPIP up to 3.1.10/3.2.4. The affected element is an unknown function of the file ecrire/inc/meta.php. The manipulation leads to authorization. This vulnerability is uniquely identified as CVE-2019-16391. The attack is possible to be carried out remotely. No exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability was found in SPIP up to 3.1.10/3.2.4 (Content Management System) and classified as critical. This issue affects some unknown processing of the file ecrire/inc/meta.php. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-863. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
SPIP before 3.1.11 and 3.2 before 3.2.5 allows authenticated visitors to modify any published content and execute other modifications in the database. This is related to ecrire/inc/meta.php and ecrire/inc/securiser_action.php.
The weakness was disclosed 09/17/2019 (Website). The advisory is shared at seclists.org. The identification of this vulnerability is CVE-2019-16391 since 09/17/2019. The attack may be initiated remotely. Required for exploitation is a simple authentication. Technical details are known, but no exploit is available.
By approaching the search of inurl:ecrire/inc/meta.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 3.1.11 or 3.2.5 eliminates this vulnerability.
The entries VDB-141920, VDB-141918 and VDB-141919 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.2
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
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: AuthorizationCWE: CWE-863 / CWE-285 / CWE-266
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: SPIP 3.1.11/3.2.5
Patch: git.spip.net
Timeline
09/17/2019 🔍09/17/2019 🔍
09/18/2019 🔍
12/26/2023 🔍
Sources
Advisory: 187952ce85e73b52c2753f2d54fc2c44807b8f79Status: Not defined
CVE: CVE-2019-16391 (🔍)
GCVE (CVE): GCVE-0-2019-16391
GCVE (VulDB): GCVE-100-141917
See also: 🔍
Entry
Created: 09/18/2019 08:55Updated: 12/26/2023 08:32
Changes: 09/18/2019 08:55 (56), 08/28/2020 16:31 (1), 12/26/2023 08:31 (5), 12/26/2023 08:32 (1)
Complete: 🔍
Cache ID: 216::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.