feat(fetcher): add nuclei

[MaineK00n]

If this Pull Request is work in progress, Add a prefix of “[WIP]” in the title.

What did you implement:

add nuclei

Type of change

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

$ go-exploitdb fetch nuclei
INFO[12-15|04:56:19] Fetching Nuclei Templates 
INFO[12-15|04:56:20] Nuclei Templates                         count=3628
INFO[12-15|04:56:20] Inserting Nuclei Templates into DB 
INFO[12-15|04:56:20] Inserting 3628 Exploits 
INFO[12-15|04:56:20] Inserting new Exploits 
3628 / 3628 [---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------] 100.00% ? p/s
INFO[12-15|04:56:20] No CveID Exploit Count                   count=0
INFO[12-15|04:56:20] CveID Exploit Count                      count=3628

$ go-exploitdb search --type CVE --param CVE-2025-49844

Results: 
---------------------------------------

[*]CVE-ExploitID Reference:
  CVE: CVE-2025-49844
  Exploit Type: Nuclei
  Exploit Unique ID: Nuclei-5e210979e211a5e6aa9bc35dff0d5f12
  URL: https://github.com/projectdiscovery/nuclei-templates/blob/main/javascript/cves/2025/CVE-2025-49844.yaml
  Description: Redis is an open source, in-memory database that persists on disk. Versions 8.2.1 and below allow an authenticated user to use a specially crafted Lua script to manipulate the garbage collector, trigger a use-after-free and potentially lead to remote code execution. The problem exists in all versions of Redis with Lua scripting. This issue is fixed in version 8.2.2. To workaround this issue without patching the redis-server executable is to prevent users from executing Lua scripts. This can be done using ACL to restrict EVAL and EVALSHA commands.


[*]Exploit Detail Info: ---------------------------------------

Checklist:

You don't have to satisfy all of the following.

• Write tests
• Write documentation
• Check that there aren't other open pull requests for the same issue/feature
• Format your source code by make fmt
• Pass the test by make test
• Provide verification config / commands
• Enable "Allow edits from maintainers" for this PR
• Update the messages below

Is this ready for review?: YES

Reference

[shino]

🍻