CVE-2015-10137

None

Github link:
https://github.com/Kai-One001/-CVE-2015-10137-WordPress-N-Media-Website-Contact-Form-with-File-Upload-1.3.4

CVE-2025-53770

None

Github link:
https://github.com/Lapesha/CVE-2025-53770

CVE-2024-4577

In PHP versions 8.1.* before 8.1.29, 8.2.* before 8.2.20, 8.3.* before 8.3.8, when using Apache and PHP-CGI on Windows, if the system is set up to use certain code pages, Windows may use "Best-Fit" behavior to replace characters in command line given to Win32 API functions. PHP CGI module may misinterpret those characters as PHP options, which may allow a malicious user to pass options to PHP binary being run, and thus reveal the source code of scripts, run arbitrary PHP code on the server, etc.

Github link:
https://github.com/CirqueiraDev/MassExploit-CVE-2024-4577

CVE-2025-53770

None

Github link:
https://github.com/b33b0y/CVE-2025-53770

CVE-2025-5777

Insufficient input validation leading to memory overread when the NetScaler is configured as a Gateway (VPN virtual server, ICA Proxy, CVPN, RDP Proxy) OR AAA virtual server

Github link:
https://github.com/Shivshantp/CVE-2025-5777-TrendMicro-ApexCentral-RCE

CVE-2025-53770

None

Github link:
https://github.com/Hassanopop/CVE-2025-53770

CVE-2023-2598

A flaw was found in the fixed buffer registration code for io_uring (io_sqe_buffer_register in io_uring/rsrc.c) in the Linux kernel that allows out-of-bounds access to physical memory beyond the end of the buffer. This flaw enables full local privilege escalation.

Github link:
https://github.com/SpongeBob-369/CVE-2023-2598

CVE-2024-4947

Type Confusion in V8 in Google Chrome prior to 125.0.6422.60 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)

Github link:
https://github.com/DiabloX90911/CVE-2024-4947

CVE-2024-38063

Windows TCP/IP Remote Code Execution Vulnerability

Github link:
https://github.com/Skac44/CVE-2024-38063

CVE-2025-53770

None

Github link:
https://github.com/Kamal-Hegazi/CVE-2025-53770-SharePoint-RCE

CVE-2025-29927

Next.js is a React framework for building full-stack web applications. Starting in version 1.11.4 and prior to versions 12.3.5, 13.5.9, 14.2.25, and 15.2.3, it is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware. If patching to a safe version is infeasible, it is recommend that you prevent external user requests which contain the x-middleware-subrequest header from reaching your Next.js application. This vulnerability is fixed in 12.3.5, 13.5.9, 14.2.25, and 15.2.3.

Github link:
https://github.com/Kamal-Hegazi/CVE-2025-29927-Next.js-Middleware-Authorization-Bypass

CVE-2025-50777

None

Github link:
https://github.com/veereshgadige/aziot-cctv-cve-2025-50777

CVE-2024-10858

None

Github link:
https://github.com/iamarit/CVE-2024-10858

CVE-2025-30397

Access of resource using incompatible type ('type confusion') in Microsoft Scripting Engine allows an unauthorized attacker to execute code over a network.

Github link:
https://github.com/B1ack4sh/Blackash-CVE-2025-30397

CVE-2025-53770

None

Github link:
https://github.com/m4r1x/CVE-2025-53770-Scanner

CVE-2024-6387

A signal handler race condition was found in OpenSSH's server (sshd), where a client does not authenticate within LoginGraceTime seconds (120 by default, 600 in old OpenSSH versions), then sshd's SIGALRM handler is called asynchronously. However, this signal handler calls various functions that are not async-signal-safe, for example, syslog().

Github link:
https://github.com/xiw1ll/CVE-2024-6387_Checker

CVE-2021-45046

It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allows attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in an information leak and remote code execution in some environments and local code execution in all environments. Log4j 2.16.0 (Java 8) and 2.12.2 (Java 7) fix this issue by removing support for message lookup patterns and disabling JNDI functionality by default.

Github link:
https://github.com/ifconfig-me/Log4Shell-Payloads

CVE-2025-8018

None

Github link:
https://github.com/drackyjr/CVE-2025-8018

CVE-2025-29774

None

Github link:
https://github.com/demining/Digital-Signature-Forgery-Attack

CVE-2025-53770

None

Github link:
https://github.com/zach115th/ToolShellFinder