| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in PBBoard 2.1.4. The affected element is an unknown function of the file index.php of the component User Account. The manipulation leads to access control. This vulnerability is traded as CVE-2012-4035. Furthermore, there is an exploit available.
Details
A vulnerability was found in PBBoard 2.1.4 (Forum Software) and classified as critical. This issue affects some unknown processing of the file index.php of the component User Account. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-264. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
The new_password page in PBBoard 2.1.4 allows remote attackers to change the password of arbitrary user accounts via the member_id and new_password parameters to index.php.
The weakness was shared 08/11/2012 with High-Tech Bridge Security Research Lab (Website). The advisory is shared at htbridge.com. The identification of this vulnerability is CVE-2012-4035 since 07/20/2012. 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 as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1068 for this issue.
The exploit is available at securityfocus.com. It is declared as proof-of-concept. By approaching the search of inurl:index.php it is possible to find vulnerable targets with Google Hacking.
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 databases at X-Force (77506), Exploit-DB (37615), SecurityFocus (BID 54916†), OSVDB (84481†) and Secunia (SA50153†). The entries VDB-61917 and VDB-61528 are related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.6
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
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: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
07/20/2012 🔍08/08/2012 🔍
08/11/2012 🔍
08/11/2012 🔍
03/23/2015 🔍
02/13/2025 🔍
Sources
Advisory: htbridge.comOrganization: High-Tech Bridge Security Research Lab
Status: Not defined
CVE: CVE-2012-4035 (🔍)
GCVE (CVE): GCVE-0-2012-4035
GCVE (VulDB): GCVE-100-61529
X-Force: 77506
SecurityFocus: 54916 - PBBoard Multiple Security Vulnerabilities
Secunia: 50153
OSVDB: 84481
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 03/23/2015 16:50Updated: 02/13/2025 02:09
Changes: 03/23/2015 16:50 (57), 02/19/2019 11:55 (2), 02/13/2025 02:09 (21)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.