CVE mentions, exploit signals, and PoC evidence in one fast public view.
Loading current evidence
Historical archive search
Search decades of CVEs by regex, severity, date, CWE, vendor/product tags, KEV, PoC, and other evidence.
Results
3,082 results · Sorted by Highest Buzz score first
Administrator routes and install/update/uninstall processing did not consistently enforce component-management and installation permissions. An unauthorized backend user or CSRF a…
Smart Search indexing could render generated content using the indexing administrator’s identity instead of a public guest. Restricted or administrator-only content could conseque…
Content tags could use ignore flags or property overrides to render restricted or unpublished articles or modules. A content author could thereby expose content to visitors who la…
User tags, filters and conditions allowed access to insufficiently restricted user fields. Crafted content could expose authentication-related data, raw user parameters or restric…
Tag-provided custom HTML, module content/title overrides and decoded modal or tooltip values could execute unsafe markup. A content author could inject JavaScript that ran in visi…
Free did not require both the article creator and last modifier to be Super Users before executing article PHP. Pro did not consistently enforce configured CSS, JavaScript and PHP…
IP Login trusted forwarded client-IP headers without requiring a configured trusted proxy. Attackers could spoof the IP used for automatic login and potentially impersonate mapped…
Persistent URL login keys were also generated using a non-cryptographic random generator with insufficient entropy.
Content-controlled image URLs could request private or reserved network services, follow unsafe redirects and save responses without validating that they were images. This could r…
Administrator URL purges did not consistently require a valid token and cache-management permission.
Custom purge and log paths could escape the site webroot directory.
Custom query URLs could access internal or reserved network services.
CDN credentials were exposed in administrator request URLs.
GeoIP lookups trusted spoofable forwarded client-IP headers, this could cause GeoIP-rule bypass.
Database-update requests lacked consistent token and Super User checks, this could cause unauthorized updates.
An authenticated non-admin user can exploit a SQL injection flaw in the ticketing REST API to access sensitive data stored in the appliance database.
Unvalidated input in asset filter parameters allows shell metacharacters to escape command argument handling, resulting in remote code execution as a low-privileged OS user via th…
A filename supplied during file upload is not properly sanitized before being used in system command execution, allowing an attacker to inject shell metacharacters and achieve com…
Unsanitized user-supplied input in report filtering parameters is concatenated directly into SQL queries without proper escaping or parameterized queries, enabling blind SQL injec…
The audit file upload handler does not sanitize filenames, allowing shell metacharacters to flow into system command execution. This input validation failure enables command injec…
MaxMind credentials where leaked in request URLs, causing a credential leakage vulnerability.
Geo IP database update archives have been broadly extracted without path validation, leading to unsafe file extractions.
CDN versioning could check file paths outside the site directory, exposing local file existence and modification metadata.
Modals gallery paths could enumerate unintended directories.
ReReplacer XML include paths could read files outside the site directory.
Every filter state lives in the URL so you can bookmark, share, and crawl exact historical slices instead of a client-only search session.
Buzz order uses the latest all-time evidence snapshot, refreshed every two hours. Evidence-bearing CVEs rank first; records without a snapshot continue newest-first.