Teardrop Theme 1.8.1 on WordPress Option Update default permission

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.5$0-$5k0.00

Summaryinfo

A vulnerability was found in Teardrop Theme 1.8.1 on WordPress and classified as critical. This vulnerability affects unknown code of the component Option Update Handler. The manipulation results in default permission. This vulnerability is reported as CVE-2015-9476. The attack can be launched remotely. No exploit exists.

Detailsinfo

A vulnerability was found in Teardrop Theme 1.8.1 on WordPress (WordPress Plugin). It has been classified as critical. Affected is an unknown code of the component Option Update Handler. The manipulation with an unknown input leads to a default permission vulnerability. CWE is classifying the issue as CWE-276. During installation, installed file permissions are set to allow anyone to modify those files. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

The Teardrop theme 1.8.1 for WordPress has insufficient restrictions on option updates.

The weakness was disclosed 10/10/2019. This vulnerability is traded as CVE-2015-9476 since 10/10/2019. The exploitability is told to be easy. It is possible to launch the attack remotely. A authentication is needed for exploitation. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1222 by the MITRE ATT&CK project.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.6
VulDB Meta Temp Score: 7.6

VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 8.8
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Default permission
CWE: CWE-276 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

10/10/2019 🔍
10/10/2019 +0 days 🔍
10/10/2019 +0 days 🔍
01/07/2024 +1550 days 🔍

Sourcesinfo

Advisory: wpvulndb.com
Status: Not defined

CVE: CVE-2015-9476 (🔍)
GCVE (CVE): GCVE-0-2015-9476
GCVE (VulDB): GCVE-100-143322

Entryinfo

Created: 10/10/2019 21:39
Updated: 01/07/2024 15:32
Changes: 10/10/2019 21:39 (35), 09/30/2020 17:58 (18), 01/07/2024 15:32 (3)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!