Skip to content
Fencer Intel
medium 4.8

CVE-2021-3797 json

Use of Wrong Operator in String Comparison in hestiacp/hestiacp

published 5y ago modified 4mo ago also EUVD-2021-27057

cvss
4.8
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 67%
public exploits
0
none known

Summary

hestiacp is vulnerable to Use of Wrong Operator in String Comparison

Patch / fix

Is CVE-2021-3797 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.15% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • huntr.dev https://huntr.dev/bounties/c24fb15c-3c84-45c8-af04-a660f8da388f referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 4.8 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected products

  • hestiacp hestiacp/hestiacp

Classification

Weakness
  • CWE-597 Use of Wrong Operator in String Comparison

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.