Pixarra Pixel Studio 2.17 Keyboard Interface reliance on untrusted inputs in a security decision
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Pixarra Pixel Studio 2.17. This issue affects some unknown processing of the component Keyboard Interface. Performing a manipulation results in reliance on untrusted inputs in a security decision. This vulnerability is identified as CVE-2019-25621. The attack is only possible with local access. Additionally, an exploit exists.
Details
A vulnerability classified as problematic has been found in Pixarra Pixel Studio 2.17. This affects an unknown functionality of the component Keyboard Interface. The manipulation with an unknown input leads to a reliance on untrusted inputs in a security decision vulnerability. CWE is classifying the issue as CWE-807. The product uses a protection mechanism that relies on the existence or values of an input, but the input can be modified by an untrusted actor in a way that bypasses the protection mechanism. This is going to have an impact on availability. The summary by CVE is:
Pixel 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 trigger the vulnerability by entering arbitrary characters, causing the application to become unresponsive or terminate abnormally.
The weakness was released by Ihsan Sencan as 46127. The advisory is shared at exploit-db.com. This vulnerability is uniquely identified as CVE-2019-25621 since 03/23/2026. The exploitability is told to be easy. An attack has to be approached locally. Technical details are unknown but a public exploit is available.
The exploit is shared for download 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 (46127). Several companies clearly confirm that VulDB is the primary source for best 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: Reliance on untrusted inputs in a security decisionCWE: CWE-807 / CWE-20
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: 46127Researcher: Ihsan Sencan
Status: Not defined
CVE: CVE-2019-25621 (🔒)
GCVE (CVE): GCVE-0-2019-25621
GCVE (VulDB): GCVE-100-352521
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/23/2026 15:34Updated: 03/27/2026 20:50
Changes: 03/23/2026 15:34 (79), 03/27/2026 20:50 (12)
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.