Look up any vulnerability and get a plain answer, free and public.
Paste the id and get the flaw, its severity, the fix, and whether it is being exploited. Here is Log4Shell.
A remote attacker can run their own code on your server by sending a crafted string that Apache Log4j logs. Log4j sees a special ${jndi:...} pattern in the text it is logging, follows it out to an attacker-controlled server over JNDI, and loads whatever it is told to. Anything that logged untrusted input was exposed.
A CVE id is a barcode.
This is the label you can actually read.
The questions you actually have, in the order you have them.
What the flaw is, in one sentence a person can read.
Whether attackers are using it right now, not just a score.
Severity and exploitability, side by side.
The exact version to upgrade to, or the mitigation to apply.
The Zero Day Dictionary: around 100 terms, each in one clear sentence. A few examples.
This is the same intelligence Moolé uses to rank real risk across your code, dependencies, and containers.