WikkaWiki 1.3.1/1.3.2 Logging ⚔ [Disputed]

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.
5.1$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic has been found in WikkaWiki 1.3.1/1.3.2. Affected by this issue is some unknown functionality of the component Logging. Performing a manipulation results in an unknown weakness. This vulnerability is cataloged as CVE-2011-4451. Furthermore, there is an exploit available. The real existence of this vulnerability is still doubted at the moment.

Detailsinfo

A vulnerability classified as problematic has been found in WikkaWiki 1.3.1/1.3.2 (Content Management System). This affects some unknown processing of the component Logging. This is going to have an impact on integrity. The summary by CVE is:

** DISPUTED ** libs/Wakka.class.php in WikkaWiki 1.3.1 and 1.3.2, when the spam_logging option is enabled, allows remote attackers to write arbitrary PHP code to the spamlog_path file via the User-Agent HTTP header in an addcomment request. NOTE: the vendor disputes this issue because the rendering of the spamlog_path file never uses the PHP interpreter.

The weakness was shared 09/05/2012 (Website). It is possible to read the advisory at wush.net. This vulnerability is uniquely identified as CVE-2011-4451 since 11/15/2011. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are unknown but a public exploit is available.

The exploit is shared for download at exploit-db.com. It is declared as highly functional. The real existence of this vulnerability is still doubted at the moment.

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

The vulnerability is also documented in the vulnerability database at Exploit-DB (18177). The entries VDB-62020, VDB-62018, VDB-62017 and VDB-62016 are related to this item. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.1

VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Unknown
CWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Highly functional
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

MetaSploit ID: wikka_spam_exec.rb
MetaSploit Name: WikkaWiki 1.3.2 Spam Logging PHP Injection
MetaSploit File: 🔍

D2Sec: WikkaWiki 1.3.1 SQL Injection

Exploit-DB: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

11/15/2011 🔍
09/05/2012 +295 days 🔍
09/05/2012 +0 days 🔍
03/23/2015 +929 days 🔍
01/26/2025 +3597 days 🔍

Sourcesinfo

Advisory: 1098
Status: Not defined
Disputed: 🔍

CVE: CVE-2011-4451 (🔍)
GCVE (CVE): GCVE-0-2011-4451
GCVE (VulDB): GCVE-100-62019
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍

Entryinfo

Created: 03/23/2015 16:50
Updated: 01/26/2025 07:58
Changes: 03/23/2015 16:50 (44), 01/29/2018 16:08 (1), 12/13/2021 07:15 (2), 12/13/2021 07:20 (7), 08/07/2024 05:19 (15), 01/26/2025 07:58 (10)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!