| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.3 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in PhpMyFactures and classified as problematic. Affected by this issue is some unknown functionality of the file ajouter_remise.php. Performing a manipulation results in information disclosure. There is no exploit available.
Details
A vulnerability was found in PhpMyFactures (the affected version unknown). It has been classified as problematic. This affects an unknown part of the file ajouter_remise.php. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality.
The weakness was shared 06/10/2006 by DarkFig (Website). The advisory is shared at acid-root.new.fr. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
After before and not just, there has been an exploit disclosed. By approaching the search of inurl:ajouter_remise.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 OSVDB (26488†) and Secunia (SA20642†). The entries VDB-30880, VDB-30879, VDB-30878 and VDB-30877 are related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.3VulDB Meta Temp Score: 3.3
VulDB Base Score: 3.3
VulDB Temp Score: 3.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: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
Google Hack: 🔍
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
06/10/2006 🔍06/10/2006 🔍
06/14/2006 🔍
05/08/2016 🔍
12/04/2018 🔍
Sources
Advisory: acid-root.new.frResearcher: DarkFig
Status: Not defined
GCVE (VulDB): GCVE-100-84129
Secunia: 20642
OSVDB: 26488 - PhpMyFactures ajouter_remise.php Direct Request Path Disclosure
See also: 🔍
Entry
Created: 05/08/2016 19:46Updated: 12/04/2018 11:09
Changes: 05/08/2016 19:46 (39), 12/04/2018 11:09 (2)
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.