Pixarra Luminance Studio 2.17 Keyboard Interface improper restriction of names for files and other resources
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Pixarra Luminance Studio 2.17 and classified as problematic. The affected element is an unknown function of the component Keyboard Interface. The manipulation leads to improper restriction of names for files and other resources. This vulnerability is listed as CVE-2019-25623. The attack must be carried out locally. In addition, an exploit is available.
Details
A vulnerability, which was classified as problematic, has been found in Pixarra Luminance Studio 2.17. This issue affects an unknown part of the component Keyboard Interface. The manipulation with an unknown input leads to a improper restriction of names for files and other resources vulnerability. Using CWE to declare the problem leads to CWE-641. The product constructs the name of a file or other resource using input from an upstream component, but it does not restrict or incorrectly restricts the resulting name. Impacted is availability. The summary by CVE is:
Luminance Studio 2.17 contains a denial of service vulnerability that allows local attackers to crash the application by providing malformed input through the keyboard interface. Attackers can create a text file with arbitrary character sequences and trigger the application to process the input, causing the application to become unresponsive or terminate abnormally.
The weakness was presented by Ihsan Sencan as 46130. It is possible to read the advisory at exploit-db.com. The identification of this vulnerability is CVE-2019-25623 since 03/23/2026. The exploitation is known to be easy. Attacking locally is a requirement. Technical details are unknown but a public exploit is available.
The exploit is available at exploit-db.com. It is declared as proof-of-concept.
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 (46130). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 4.9
VulDB Base Score: 3.3
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔒
CNA Base Score: 6.2
CNA Vector (VulnCheck): 🔒
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: Improper restriction of names for files and other resourcesCWE: CWE-641
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
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
03/23/2026 Advisory disclosed03/23/2026 CVE reserved
03/23/2026 VulDB entry created
03/27/2026 VulDB entry last update
Sources
Advisory: 46130Researcher: Ihsan Sencan
Status: Not defined
CVE: CVE-2019-25623 (🔒)
GCVE (CVE): GCVE-0-2019-25623
GCVE (VulDB): GCVE-100-352523
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/23/2026 15:35Updated: 03/27/2026 20:50
Changes: 03/23/2026 15:35 (79), 03/27/2026 20:50 (12)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.