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/maxsite/cms | affected | < 08937a3c5d672a242d68f53e9fccf8a748820ef3 | vendor fix → 08937a3c5d672a242d68f53e9fccf8a748820ef3 | osv | |
| https://github.com/maxsite/cms | fixed | 08937a3c5d672a242d68f53e9fccf8a748820ef3 | vendor fix → 08937a3c5d672a242d68f53e9fccf8a748820ef3 | osv | |
| MaxSite/CMS MaxSite · CMS | affected | 109.0 | none available | cve_cna | |
| MaxSite/CMS MaxSite · CMS | affected | 109.1 | none available | cve_cna | |
| MaxSite/CMS MaxSite · CMS | not affected | 109.2 | not applicable | cve_cna |
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.