Focus on publify_project vulnerabilities and metrics.
Last updated: 08 Mar 2025, 23:25 UTC
This page consolidates all known Common Vulnerabilities and Exposures (CVEs) associated with publify_project. We track both calendar-based metrics (using fixed periods) and rolling metrics (using gliding windows) to give you a comprehensive view of security trends and risk evolution. Use these insights to assess risk and plan your patching strategy.
For a broader perspective on cybersecurity threats, explore the comprehensive list of CVEs by vendor and product. Stay updated on critical vulnerabilities affecting major software and hardware providers.
Total publify_project CVEs: 14
Earliest CVE date: 09 Jan 2020, 14:15 UTC
Latest CVE date: 29 Jan 2023, 17:15 UTC
Latest CVE reference: CVE-2023-0569
30-day Count (Rolling): 0
365-day Count (Rolling): 0
Calendar-based Variation
Calendar-based Variation compares a fixed calendar period (e.g., this month versus the same month last year), while Rolling Growth Rate uses a continuous window (e.g., last 30 days versus the previous 30 days) to capture trends independent of calendar boundaries.
Month Variation (Calendar): 0%
Year Variation (Calendar): 0%
Month Growth Rate (30-day Rolling): 0.0%
Year Growth Rate (365-day Rolling): 0.0%
Average CVSS: 3.41
Max CVSS: 6.4
Critical CVEs (≥9): 0
| Range | Count |
|---|---|
| 0.0-3.9 | 7 |
| 4.0-6.9 | 7 |
| 7.0-8.9 | 0 |
| 9.0-10.0 | 0 |
These are the five CVEs with the highest CVSS scores for publify_project, sorted by severity first and recency.
Weak Password Requirements in GitHub repository publify/publify prior to 9.2.10.
Improper Input Validation in GitHub repository publify/publify prior to 9.2.10.
Insecure Storage of Sensitive Information in GitHub repository publify/publify prior to 9.2.10.
Integer Overflow or Wraparound in GitHub repository publify/publify prior to 9.2.10.
Unrestricted Upload of File with Dangerous Type in GitHub repository publify/publify prior to 9.2.9.
Authorization Bypass Through User-Controlled Key in GitHub repository publify/publify prior to 9.2.9.
Leaking password protected articles content due to improper access control in GitHub repository publify/publify prior to 9.2.8. Attackers can leverage this vulnerability to view the contents of any password-protected article present on the publify website, compromising confidentiality and integrity of users.
Code Injection in GitHub repository publify/publify prior to 9.2.8.
Improper Access Control in GitHub repository publify/publify prior to 9.2.8.
Business Logic Errors in GitHub repository publify/publify prior to 9.2.7.
In publify, versions v8.0 to v9.2.4 are vulnerable to stored XSS as a result of an unrestricted file upload. This issue allows a user with “publisher” role to inject malicious JavaScript via the uploaded html file.
In Publify, versions v8.0 to v9.2.4 are vulnerable to stored XSS. A user with a “publisher” role is able to inject and execute arbitrary JavaScript code while creating a page/article.
In Publify, 9.0.0.pre1 to 9.2.4 are vulnerable to Improper Access Control. “guest” role users can self-register even when the admin does not allow. This happens due to front-end restriction only.
Publify before 8.0.1 is vulnerable to a Denial of Service attack