Skip to main content
VulnerabilityPublished

CVE-2025-52159: PPress · Use of Hard-coded Credentials

Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

Organizations should immediately audit their deployments of PPress to identify any instances of version 0.0.9 or other versions potentially affected by hardcoded credentials. If found, they should isolate these systems from untrusted networks and restrict access to trusted administrators only. Where possible, replace or upgrade the software to a version without this vulnerability once available. In the absence of patches, organizations can mitigate risk by changing default configurations if the software allows it or by implementing network-level controls such as firewalls, VPNs, or zero-trust segmentation to limit exposure. Monitoring and logging authentication attempts related to PPress can help detect unauthorized access attempts early. Additionally, organizations should enforce strong access controls and multi-factor authentication on surrounding systems to reduce the impact of compromised credentials. Regular vulnerability scanning and penetration testing should include checks for hardcoded credentials and default configurations. Finally, organizations should engage with the software vendor for timelines on patches and follow security advisories closely.

Description

Hardcoded credentials in default configuration of PPress 0.0.9.

References

Community reviews

Loading reviews…