Export limit exceeded: 377313 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (377313 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-81288 | 2 Wordpress, Wp Swings | 2 Wordpress, Upsell Order Bump Offer For Woocommerce | 2026-09-02 | 7.1 High |
| Unauthenticated Cross Site Scripting (XSS) in Upsell Order Bump Offer for WooCommerce <= 3.1.5 versions. | ||||
| CVE-2026-81775 | 2 Estatik, Wordpress | 2 Estatik, Wordpress | 2026-09-02 | 7.1 High |
| Unauthenticated Cross Site Scripting (XSS) in Estatik <= 4.3.4 versions. | ||||
| CVE-2026-81286 | 2 Wclovers, Wordpress | 2 Wcfm Marketplace, Wordpress | 2026-09-02 | 9.3 Critical |
| Unauthenticated SQL Injection in WCFM Marketplace <= 3.8.1 versions. | ||||
| CVE-2026-82223 | 2 Arraytics, Wordpress | 2 Wp Event Solution, Wordpress | 2026-09-02 | 6.5 Medium |
| Unauthenticated Broken Access Control in WP Event SOlution <= 4.1.22 versions. | ||||
| CVE-2026-61777 | 1 Nvidia | 2 Megatron-bridge, Nemo Megatron Bridge | 2026-09-02 | 7.8 High |
| NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure. | ||||
| CVE-2026-61778 | 1 Nvidia | 2 Megatron-bridge, Nemo Megatron Bridge | 2026-09-02 | 7.8 High |
| NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure. | ||||
| CVE-2026-61779 | 1 Nvidia | 2 Megatron-bridge, Nemo Megatron Bridge | 2026-09-02 | 7.8 High |
| NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure. | ||||
| CVE-2026-61750 | 1 Nvidia | 2 Megatron-bridge, Nemo Megatron Bridge | 2026-09-02 | 7.8 High |
| NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure. | ||||
| CVE-2026-61751 | 1 Nvidia | 2 Megatron-bridge, Nemo Megatron Bridge | 2026-09-02 | 7.8 High |
| NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure. | ||||
| CVE-2026-61752 | 1 Nvidia | 2 Megatron-bridge, Nemo Megatron Bridge | 2026-09-02 | 7.8 High |
| NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure. | ||||
| CVE-2026-61753 | 1 Nvidia | 2 Megatron-bridge, Nemo Megatron Bridge | 2026-09-02 | 7.8 High |
| NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure. | ||||
| CVE-2026-60075 | 1 Sbeck | 1 Date::manip | 2026-09-02 | 7.5 High |
| Date::Manip versions through 7.00 for Perl allow CPU exhaustion via quadratic backtracking in the unanchored time substitution in _parse_time. _parse_time removes a time from anywhere in the string with the unanchored substitution `s/$timerx/ /`, where $timerx is an auto-generated alternation of time patterns reached through a leading `(?:$atrx|^|\s+)`. The engine therefore retries the match at every position of an interior whitespace run: at each start position the leading `\s+` consumes the rest of the run greedily, the time alternation fails because the run holds no digits, and the engine backtracks a space at a time across the run before advancing the start position, which is quadratic in the length of the run. No time need be present in the string for this to happen, only a long run of whitespace, and the parse time rises about fourfold for each doubling of the run: a few kilobytes of whitespace costs seconds of CPU per parse and tens of kilobytes costs minutes. Any caller that passes an untrusted string of unbounded length to ParseDate(), Date::Manip::Date->parse() or ->parse_time() can be made to spend unbounded CPU in a single parse, a denial of service. | ||||
| CVE-2026-61754 | 1 Nvidia | 2 Megatron-bridge, Nemo Megatron Bridge | 2026-09-02 | 7.8 High |
| NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure. | ||||
| CVE-2026-60074 | 1 Sbeck | 1 Date::manip | 2026-09-02 | 7.5 High |
| Date::Manip versions through 7.00 for Perl return corrupted dates via non-ASCII decimal digits that pass the numeric range tests in check. The parse regexes capture year, month and day with the `\d` shorthand, which on a character string matches the whole Unicode decimal digit property `\p{Nd}` and not just `[0-9]`. Date::Manip::Base::check then validates the captured fields with numeric comparisons alone (`$y<1 || $y>9999`, `$m<1 || $m>12`, `$d<1 || $d>$days`), and _parse_check stores the numified fields (`$y+0`). Perl truncates a string at the first character that is not an ASCII digit, so a field whose leading characters are ASCII digits numifies to an in-range prefix and satisfies every test: a year field of three ASCII digits followed by U+0664 ARABIC-INDIC DIGIT FOUR numifies to 202, giving the year 0202, and one non-ASCII digit in the month or day field shifts those fields the same way. The hour, minute and second fields match explicit ASCII character classes (`0?[0-9]`, `[0-5][0-9]`) and do not shift, though a non-ASCII digit in a fractional hour or minute field truncates the fraction. Any caller that passes an untrusted character string to ParseDate() or Date::Manip::Date->parse() can get back a date that differs from the string it parsed, with no parse error. Where the parsed date gates logic such as an expiry check or a retention window, the shift goes unnoticed. | ||||
| CVE-2026-61755 | 1 Nvidia | 2 Megatron-bridge, Nemo Megatron Bridge | 2026-09-02 | 7.8 High |
| NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure. | ||||
| CVE-2026-61756 | 1 Nvidia | 2 Megatron-bridge, Nemo Megatron Bridge | 2026-09-02 | 7.8 High |
| NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure. | ||||
| CVE-2026-61757 | 1 Nvidia | 2 Megatron-bridge, Nemo Megatron Bridge | 2026-09-02 | 7.8 High |
| NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure. | ||||
| CVE-2026-61758 | 1 Nvidia | 2 Megatron-bridge, Nemo Megatron Bridge | 2026-09-02 | 7.8 High |
| NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure. | ||||
| CVE-2026-61759 | 1 Nvidia | 2 Megatron-bridge, Nemo Megatron Bridge | 2026-09-02 | 7.8 High |
| NVIDIA Megatron Bridge contains a vulnerability where an attacker could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure. | ||||
| CVE-2026-84699 | 1 Teampasswordmanager | 1 Team Password Manager | 2026-09-02 | 9.1 Critical |
| Team Password Manager before 14.184.308 fails to enforce authentication requirements in the local account password reset flow. Unauthenticated attackers can reset local account passwords and authenticate as those users to gain unauthorized access. | ||||