Adding vulnerability description alongside CVE

[bernard-yip]

Is your feature request related to a problem? Please describe.
When looking for nuclei templates to write, it is frustrating to scour through the list to read the description of each CVE to identify if there's value in writing a nuclei template.

Describe the solution you'd like
I want to append the description of the CVE to the output so I can read through the output and determine which CVEs I can write nuclei templates for.

Describe alternatives you've considered
There is no alternate solution, but I have an edited script that appends the CVE description below the output. This can also be output to a different folder for reference instead of overriding the current file format.

For example:

[ CVE-2024-37763 ] [ cross-site scripting ] [ https://github.com/trickest/cve/blob/main/2024/CVE-2024-37763.md ]
MachForm up to version 19 is affected by an unauthenticated stored cross-site scripting which affects users with valid sessions whom can view compiled forms results.

Additional context
I understand doing this would cause issues with the categories' counts. We can add filters to ensure that the lines we are counting is of a specific format ([ CVE ] [ CATEGORY ] GITHUB_LINK) before counting the CVE.

[edoardottt]

Hi @bernard-yip ! Thanks for your contribution.
Maybe the best thing to insert this would be adding a different folder? Like raw or something like this?
let me know what you think

[bernard-yip]

@edoardottt appreciate your reply! Will do some testing and create the folders if you're interested.

If you'd like, I could format them as json so it addresses #4 . I'll spin up a PR soon!