Skip to content
CORVASEC — Knowledge Defends
CORVASEC INTELLIGENCE ENGINE

Intelligence Explorer

Investigate synchronized vulnerability intelligence and vetted campaign intelligence from one workspace. Move between CVEs, exploitation context, campaigns, actors, sectors, confidence and ATT&CK relationships without mixing fundamentally different intelligence records.

▤
Indexed CVEs83,462CVEs currently synchronized
⬡
Critical CVEs7,543Across the synchronized dataset
⚑
CISA KEV1,786Known exploited vulnerabilities
♧
MITRE ATT&CK706Techniques + sub-techniques
Last synchronized 51 minutes ago · automatic refresh every 10 min
▤

Vulnerability Intelligence Directory

Explore and search through 83,462 vulnerability records.

77,869–77,880 of 83,462 records

A vulnerability has been found in JD Cloud BE6500 4.4.1.r4308. This issue affects the function sub_4780 of the file /jdcapi. Such manipulation of the argument ddns_name leads to command injection. The attack may be perfo...

▢  Published Dec 25, 2025 ↻  Updated Oct 7, 2026
View details  →

Pexip Infinity 35.0 through 38.1 before 39.0, in non-default configurations that use Direct Media for WebRTC, has Improper Input Validation in signalling that allows an attacker to trigger a software abort, resulting in...

▢  Published Dec 25, 2025 ↻  Updated Oct 7, 2026
View details  →

Pexip Infinity before 39.0 has Improper Input Validation in the media implementation, allowing a remote attacker to trigger a software abort via a crafted media stream, resulting in a denial of service.

▢  Published Dec 25, 2025 ↻  Updated Oct 7, 2026
View details  →
!CVE-2025-66378MEDIUM 5.9

Pexip Infinity 38.0 and 38.1 before 39.0 has insufficient access control in the RTMP implementation, allowing an attacker to disconnect RTMP streams traversing a Proxy Node.

▢  Published Dec 25, 2025 ↻  Updated Oct 7, 2026
View details  →

Pexip Infinity before 39.0 has Missing Authentication for a Critical Function in a product-internal API, allowing an attacker (who already has access to execute code on one node within a Pexip Infinity installation) to i...

▢  Published Dec 25, 2025 ↻  Updated Oct 7, 2026
View details  →

Pexip Infinity 15.0 through 38.0 before 38.1 has Improper Access Control in the Secure Scheduler for Exchange service, when used with Office 365 Legacy Exchange Tokens. This allows a remote attacker to read potentially s...

▢  Published Dec 25, 2025 ↻  Updated Oct 7, 2026
View details  →
!CVE-2025-49088MEDIUM 5.9

Pexip Infinity 32.0 through 37.1 before 37.2, in certain configurations of OTJ (One Touch Join) for Teams SIP Guest Join, has Improper Input Validation in the OTJ service, allowing a remote attacker to trigger a software...

▢  Published Dec 25, 2025 ↻  Updated Oct 7, 2026
View details  →

Pexip Infinity 35.0 through 37.2 before 38.0 has Improper Input Validation in signalling that allows an attacker to trigger a software abort, resulting in a denial of service.

▢  Published Dec 25, 2025 ↻  Updated Oct 7, 2026
View details  →

Pexip Infinity 33.0 through 37.0 before 37.1 has improper input validation in signaling that allows an attacker to trigger a software abort, resulting in a denial of service.

▢  Published Dec 25, 2025 ↻  Updated Oct 7, 2026
View details  →

Pexip Infinity before 37.0 has improper input validation in signalling that allows a remote attacker to trigger a software abort via a crafted signalling message, resulting in a denial of service.

▢  Published Dec 25, 2025 ↻  Updated Oct 7, 2026
View details  →
!CVE-2025-15078MEDIUM 5.5

A vulnerability was detected in itsourcecode Student Management System 1.0. The impacted element is an unknown function of the file /list_report.php. The manipulation of the argument sy results in sql injection. The atta...

▢  Published Dec 25, 2025 ↻  Updated Oct 7, 2026
View details  →
!CVE-2025-15077MEDIUM 5.5

A security vulnerability has been detected in itsourcecode Student Management System 1.0. The affected element is an unknown function of the file /form137.php. The manipulation of the argument ID leads to sql injection....

▢  Published Dec 25, 2025 ↻  Updated Oct 7, 2026
View details  →

Catalog counts represent locally imported records and depend on the most recent successful synchronization.