Every applicability statement published about this vulnerability, kept as each source wrote it rather than merged into one verdict. Where sources disagree, both positions are shown.
A statement that names no version covers the whole product, which is not the same as your version falling inside a range. Orderings marked best effort come from schemes with no published comparison algorithm; exact ones follow a published specification.
Precedence decides which claim wins when two sources describe the same product over the same version range. It is a property of the source, not of the claim, and changing it re-ranks the data without re-reading a single document.
| Product | Status | Versions | Remediation | Source | |
|---|---|---|---|---|---|
| https://github.com/usmannasir/cyberpanel | affected | < 1c0c6cbcf71abe573da0b5fddfb9603e7477f683 | vendor fix → 1c0c6cbcf71abe573da0b5fddfb9603e7477f683 | osv | |
| https://github.com/usmannasir/cyberpanel | fixed | 1c0c6cbcf71abe573da0b5fddfb9603e7477f683 | vendor fix → 1c0c6cbcf71abe573da0b5fddfb9603e7477f683 | osv | |
| n/a/n/a n/a · n/a | affected | no version stated vendor label: all versions | none available | cve_cna | |
| cyberpanel/cyberpanel cyberpanel · cyberpanel | affected | < 2.3.9 | none available | cve_adp |
A claim with no version range is shown as written rather than expanded: a government catalog naming only a vendor and product is a real statement at zero granularity, and inventing bounds for it would put precision in the record that the source never offered.