NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
67 matching advisories · page 1 of 3Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.1 CVE-2026-50745 A missing sanitisation vulnerability exists with user input in the stats-video.php script. revive-adserver · revive_adserver 2026-06-26 medium4.3 CVE-2026-50744 A bypass to the admin‑only restriction of the XML‑RPC API in Revive Adserver 6.0.7. revive-adserver · revive_adserver 2026-06-26 medium5.4 CVE-2026-50742 A stored XSS vulnerabilities exists in the `maintenance-acl-check.php` and `maintenance-banners-check.php` tools of Revive Adserver 6.0.7. revive-adserver · revive_adserver 2026-06-26 high8.8 CVE-2026-50741 Bypass to the fix for CVE-2026-34916. revive-adserver · revive_adserver 2026-06-26 medium5.4 CVE-2026-50740 A missing sanitisation vulnerability of user input in the zone-include.php script exists in Revive Adserver 6.0.7 and earlier. revive-adserver · revive_adserver 2026-06-26 medium4.3 CVE-2026-50739 A bypass for CVE‑2026‑34913 exists with proper ownership validation that had not been applied to the reverse operation of linking campaigns and trackers throug… revive-adserver · revive_adserver 2026-06-26 medium6.1 CVE-2023-53931 Revive Adserver 5.4.1 contains a cross-site scripting vulnerability in the banner advanced configuration page that allows attackers to inject malicious scripts. revive-adserver · revive_adserver 2025-12-17 medium6.1 CVE-2025-55124 Improper neutralisation of input in Revive Adserver 6.0.0+ causes a reflected XSS attack in the banner-zone.php script. revive-adserver · revive_adserver 2025-11-20 medium5.4 CVE-2025-55123 Improper neutralization of input in Revive Adserver 5.5.2 and 6.0.1 and earlier versions causes manager accounts to be able to craft XSS attacks to their own a… revive-adserver · revive_adserver 2025-11-20 medium4.3 CVE-2025-52671 Debug information disclosure in the SQL error message to in Revive Adserver 5.5.2 and 6.0.1 and earlier versions causes non-admin users to acquire information … revive-adserver · revive_adserver 2025-11-20 medium6.5 CVE-2025-52670 Missing authorization check in Revive Adserver 5.5.2 and 6.0.1 and earlier versions causes users on the system to delete banners owned by other accounts revive-adserver · revive_adserver 2025-11-20 medium4.3 CVE-2025-52669 Insecure design policies in the user management system of Revive Adserver 5.5.2 and 6.0.1 and earlier versions causes non-admin users to have access to the con… revive-adserver · revive_adserver 2025-11-20 medium5.4 CVE-2025-52668 Improper input neutralization in the stats-conversions.php script in Revive Adserver 5.5.2 and 6.0.1 and earlier versions causes potential information disclosu… revive-adserver · revive_adserver 2025-11-20 medium5.4 CVE-2025-52667 Missing JSON Content-Type header in a script in Revive Adserver 6.0.1 and 5.5.2 and earlier versions causes a stored XSS attack to be possible for a logged in … revive-adserver · revive_adserver 2025-11-20 low2.7 CVE-2025-52666 Improper neutralisation of format characters in the settings of Revive Adserver 5.5.2 and 6.0.1 and earlier versions causes an administrator user to disable th… revive-adserver · revive_adserver 2025-11-20 medium6.1 CVE-2025-48987 Improper Neutralization of Input in Revive Adserver 5.5.2 and 6.0.1 and earlier versions causes a potential reflected XSS attack. revive-adserver · revive_adserver 2025-11-20 high8.8 CVE-2025-48986 Authorization bypass in Revive Adserver 5.5.2 and 6.0.1 and earlier versions causes an logged in attacker to change other users' email address and potentialy t… revive-adserver · revive_adserver 2025-11-20 high8.8 CVE-2025-52664 SQL injection in Revive Adserver 6.0.0 causes potential disruption or information access when specifically crafted payloads are sent by logged in users revive-adserver · revive_adserver 2025-10-31 medium6.1 CVE-2025-27208 A reflected Cross-Site Scripting (XSS) vulnerability has been identified in Revive Adserver version 5.5.2. revive-adserver · revive_adserver 2025-10-31 medium6.5 CVE-2025-23802 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in SteveSoehl WP-Revive Adserver wp-revive-adserver allows S… WP-Revive Adserver: from n/a through 2025-01-16 medium6.1 CVE-2023-38040 A reflected XSS vulnerability exists in Revive Adserver 5.4.1 and earlier versions.. revive-adserver · revive_adserver 2023-09-17 high7.1 CVE-2021-22948 Vulnerability in the generation of session IDs in revive-adserver < 5.3.0, based on the cryptographically insecure uniqid() PHP function. revive-adserver · revive_adserver 2021-09-23 medium6.1 CVE-2021-22889 Revive Adserver before v5.2.0 is vulnerable to a reflected XSS vulnerability in the `statsBreakdown` parameter of stats.php (and possibly other scripts) due to… revive-adserver · revive_adserver 2021-03-25 medium6.1 CVE-2021-22888 Revive Adserver before v5.2.0 is vulnerable to a reflected XSS vulnerability in the `status` parameter of campaign-zone-zones.php. revive-adserver · revive_adserver 2021-03-25 medium6.1 CVE-2021-22875 Revive Adserver before 5.1.1 is vulnerable to a reflected XSS vulnerability in stats.php via the `setPerPage` parameter. revive-adserver · revive_adserver 2021-01-28 medium6.1 CVE-2021-22874 Revive Adserver before 5.1.1 is vulnerable to a reflected XSS vulnerability in userlog-index.php via the `period_preset` parameter. revive-adserver · revive_adserver 2021-01-28 medium6.1 CVE-2021-22873 Revive Adserver before 5.1.0 is vulnerable to open redirects via the `dest`, `oadest`, and/or `ct0` parameters of the lg.php and ck.php delivery scripts. revive-adserver · revive_adserver 2021-01-26 medium6.1 CVE-2021-22872 Revive Adserver before 5.1.0 is vulnerable to a reflected cross-site scripting (XSS) vulnerability via the publicly accessible afr.php delivery script. revive-adserver · revive_adserver 2021-01-26 medium4.8 CVE-2021-22871 Revive Adserver before 5.1.0 permits any user with a manager account to store possibly malicious content in the URL website property, which is then displayed u… revive-adserver · revive_adserver 2021-01-26 medium6.1 CVE-2020-8143 An Open Redirect vulnerability was discovered in Revive Adserver version < 5.0.5 and reported by HackerOne user hoangn144. revive-adserver · revive_adserver 2020-04-03

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.