Psyprax's vulnerability footprint centers on its primary product and reflects a pattern of cryptographic and access-control weaknesses, including inadequate encryption strength, incorrect permission assignment, insecure default initialization, and insufficiently protected credentials. Treat this as a focused vendor profile; live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Psyprax over time
Signals from CVEs in this vendor scope (3 CVEs).
3 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2020-10552HIGH An issue was discovered in Psyprax before 3.2.2. The Firebird database is accessible with the default user sysdba and password masterke after installation. This allows any user to | Feb 5, 2021 | 8.1 | 25 | NO | NO |
CVE-2020-10554HIGH An issue was discovered in Psyprax beforee 3.2.2. Passwords used to encrypt the data are stored in the database in an obfuscated format, which can be easily reverted. For example, | Feb 5, 2021 | 7.5 | 24 | NO | NO |
CVE-2020-10553MEDIUM An issue was discovered in Psyprax before 3.2.2. The file %PROGRAMDATA%\Psyprax32\PPScreen.ini contains a hash for the lockscreen (aka screensaver) of the application. If that entr | Feb 5, 2021 | 5.5 | 16 | NO | NO |
Signals from CVEs in this vendor scope (3 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Psyprax.
Media articles that mention a CVE ID that affects a product developed by Psyprax — matched by CVE ID, not by vendor name.