Salims Softhouse JAF CMS 4.0
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Salims Softhouse JAF CMS 4.0. It has been classified as critical. This issue affects some unknown processing. The manipulation of the argument <?php leads to memory corruption. This vulnerability is uniquely identified as CVE-2006-5131. No exploit exists.
Details
A vulnerability was found in Salims Softhouse JAF CMS 4.0 (Content Management System). It has been rated as critical. This issue affects an unknown code block. The manipulation of the argument with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:module/shout/jafshout.php (aka the shoutbox) in ph03y3nk just another flat file (JAF) CMS 4.0 RC1 allows remote attackers to execute arbitrary code within sections bounded by "<?php" and "?>", possibly due to a static code injection vulnerability involving admin/data_inc.php.
The weakness was disclosed 10/03/2006 as not defined posting (Bugtraq). The advisory is shared at securityfocus.com. The identification of this vulnerability is CVE-2006-5131 since 10/02/2006. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.
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 Secunia (SA22143†). The entries VDB-32596, VDB-32595, VDB-35431 and VDB-35430 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
09/27/2006 🔍10/02/2006 🔍
10/03/2006 🔍
10/03/2006 🔍
03/12/2015 🔍
04/23/2026 🔍
Sources
Advisory: securityfocus.com⛔Status: Not defined
CVE: CVE-2006-5131 (🔍)
GCVE (CVE): GCVE-0-2006-5131
GCVE (VulDB): GCVE-100-32597
Secunia: 22143 - JAF CMS Multiple Vulnerabilities, Highly Critical
See also: 🔍
Entry
Created: 03/12/2015 15:51Updated: 04/23/2026 12:35
Changes: 03/12/2015 15:51 (50), 09/21/2017 11:04 (3), 04/23/2026 12:35 (17)
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.