Export limit exceeded: 334498 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (334498 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2025-67291 | 1 Dotnetfoundation | 1 Piranha Cms | 2026-01-02 | 6.1 Medium |
| A stored cross-site scripting (XSS) vulnerability in the Media module of Piranha CMS v12.1 allows attackers to execute arbitrary web scripts or HTML via injecting a crafted payload into the Name field. | ||||
| CVE-2025-67418 | 2 Clipbucket, Oxygenz | 2 Clipbucket, Clipbucket | 2026-01-02 | 9.8 Critical |
| ClipBucket 5.5.2 is affected by an improper access control issue where the product is shipped or deployed with hardcoded default administrative credentials. An unauthenticated remote attacker can log in to the administrative panel using these default credentials, resulting in full administrative control of the application. | ||||
| CVE-2025-35002 | 2026-01-02 | N/A | ||
| This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||||
| CVE-2025-35001 | 2026-01-02 | N/A | ||
| This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||||
| CVE-2025-35000 | 2026-01-02 | N/A | ||
| This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||||
| CVE-2025-34999 | 2026-01-02 | N/A | ||
| This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||||
| CVE-2025-34998 | 2026-01-02 | N/A | ||
| This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||||
| CVE-2025-34997 | 2026-01-02 | N/A | ||
| This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||||
| CVE-2025-34996 | 2026-01-02 | N/A | ||
| This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||||
| CVE-2025-34995 | 2026-01-02 | N/A | ||
| This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||||
| CVE-2025-34994 | 2026-01-02 | N/A | ||
| This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||||
| CVE-2025-34993 | 2026-01-02 | N/A | ||
| This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||||
| CVE-2025-34992 | 2026-01-02 | N/A | ||
| This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||||
| CVE-2025-34991 | 2026-01-02 | N/A | ||
| This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||||
| CVE-2025-34990 | 2026-01-02 | N/A | ||
| This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||||
| CVE-2025-34989 | 2026-01-02 | N/A | ||
| This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||||
| CVE-2025-34988 | 2026-01-02 | N/A | ||
| This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||||
| CVE-2025-34987 | 2026-01-02 | N/A | ||
| This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||||
| CVE-2025-34986 | 2026-01-02 | N/A | ||
| This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||||
| CVE-2025-34985 | 2026-01-02 | N/A | ||
| This CVE ID was rejected because it was reserved but not used for a vulnerability disclosure. | ||||