Home
» Security vulnerabilities
» CVE-2023-0299
Improper Input Validation in GitHub repository publify/publify prior to 9.2.10.
NVD Status： Modified ，CVE State: published
Threat Intelligence & Risk Assessment for CVE-2023-0299
Conclusion & alert: CVE-2023-0299 is rated High Exploit Risk (74/100) : CVSS Critical severity, with medium exploitation likelihood (EPSS 0.91%).Core evidence: 1 public exploit reference(s) are indexed (Exploit-DB).Mandatory action: Public exploits are available—assess exposure, apply mitigations, and prioritize patching.
Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.
Public exploit references (Exploit-DB) for CVE-2023-0299
EDB-ID
Source
Kind
Published
Link
—
nvd_ref
exploit_tag
Exploit-DB ↗
Exploit prediction scoring system (EPSS) score for CVE-2023-0299
EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).
#
Date
Old EPSS score
New EPSS score
Delta (New - Old)
1
2026-06-15
0.35%
0.91%
+0.56%
2
2026-01-15
0.36%
0.35%
-0.01%
3
2025-11-10
—
0.36%
—
Full EPSS history
(11 records total)
Common vulnerability scoring system (CVSS) metrics for CVE-2023-0299
CVSS metrics for this CVE.
Base score
Version
Severity
Vector
Exploitability
Impact
Score source
9.8
3.1
CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
3.9
5.9
[email protected]
8.4
3.0
HIGH
CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.7
6.0
[email protected]
Weakness enumeration for CVE-2023-0299
GitHub Security Advisory for CVE-2023-0299
GHSA-q3rm-f527-ghxj · Severity: critical · Ecosystem: rubygems
— Publify Improper Input Validation vulnerability
Affected software / configurations for CVE-2023-0299
Vendor
Product
Version
Raw CPE
publify_project
publify
< 9.2.10
cpe:2.3:a:publify_project:publify:*:*:*:*:*:*:*:*
References for CVE-2023-0299
cvelogic
Threat Intelligence