Account compromise via absent password-strength validation
Published Jan 29, 2023 · Updated Mar 28, 2025
Weak password requirements in Publify before 9.2.10 allow remote attackers to compromise accounts protected by guessable passwords. The User model accepts passwords without zxcvbn strength validation across setup, signup, reset, and user-management flows. Exploitation requires an account to retain a password weak enough to guess; resulting access and privileges match those of that account.
Summary
What happened
Weak password requirements in Publify before 9.2.10 allow remote attackers to compromise accounts protected by guessable passwords. The User model accepts passwords without zxcvbn strength validation across setup, signup, reset, and user-management flows. Exploitation requires an account to retain a password weak enough to guess; resulting access and privileges match those of that account.
The record
- CVE
- CVE-2023-0569
- Published
- Jan 29, 2023
- Updated
- Mar 28, 2025
- Vendor
- Publify
- Product
- Publify
- Classifications
- CWE-521, T1110
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 29, 2023CVE publishedPublication date reported by the CVE source.
- Mar 28, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <9.2.10
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo