NetSight

Security Dashboard

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

Reset
37 matching advisories · page 1 of 2Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.2 CVE-2026-56785 FlatPress contains a stored cross-site scripting vulnerability in comment and contact forms where name, URL, and email fields are rendered without proper outpu… 2026-06-23 medium4.8 CVE-2025-44108 A stored Cross-Site Scripting (XSS) vulnerability exists in the administration panel of Flatpress CMS before 1.4 via the gallery captions component. flatpress · flatpress 2025-05-19 medium6.1 CVE-2025-29602 flatpress 1.3.1 is vulnerable to Cross Site Scripting (XSS) in Administration area via Manage categories. flatpress · flatpress 2025-05-07 high8.0 CVE-2024-9847 FlatPress CMS version latest is vulnerable to Cross-Site Request Forgery (CSRF) attacks that allow an attacker to enable or disable plugins on behalf of a vict… flatpress · flatpress 2025-03-20 medium5.4 CVE-2024-9699 A vulnerability in the file upload functionality of the FlatPress CMS admin panel (version latest) allows an attacker to upload a file with a JavaScript payloa… flatpress · flatpress 2025-03-20 high8.1 CVE-2024-4023 A stored cross-site scripting (XSS) vulnerability exists in flatpressblog/flatpress version 1.3. flatpress · flatpress 2025-03-20 medium4.8 CVE-2025-25460 A stored Cross-Site Scripting (XSS) vulnerability was identified in FlatPress 1.3.1 within the "Add Entry" feature. flatpress · flatpress 2025-02-24 high8.1 CVE-2024-41290 FlatPress CMS v1.3.1 1.3 was discovered to use insecure methods to store authentication data via the cookie's component. flatpress · flatpress 2024-10-02 medium5.4 CVE-2024-33210 A cross-site scripting (XSS) vulnerability has been identified in Flatpress 1.3. flatpress · flatpress 2024-10-02 medium5.4 CVE-2024-33209 FlatPress v1.3 is vulnerable to Cross Site Scripting (XSS). flatpress · flatpress 2024-10-02 medium4.8 CVE-2024-31835 Cross Site Scripting vulnerability in flatpress CMS Flatpress v1.3 allows a remote attacker to execute arbitrary code via a crafted payload to the file name pa… flatpress · flatpress 2024-10-01 medium6.1 CVE-2024-25412 A cross-site scripting (XSS) vulnerability in Flatpress v1.3 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the … flatpress · flatpress 2024-09-27 medium6.1 CVE-2024-25411 A cross-site scripting (XSS) vulnerability in Flatpress v1.3 allows attackers to execute arbitrary web scripts or HTML via a crafted payload injected into the … flatpress · flatpress 2024-09-27 medium4.8 CVE-2023-1148 Cross-site Scripting (XSS) - Stored in GitHub repository flatpressblog/flatpress prior to 1.3. flatpress · flatpress 2023-03-02 medium5.4 CVE-2023-1147 Cross-site Scripting (XSS) - Stored in GitHub repository flatpressblog/flatpress prior to 1.3. flatpress · flatpress 2023-03-02 medium5.4 CVE-2023-1146 Cross-site Scripting (XSS) - Generic in GitHub repository flatpressblog/flatpress prior to 1.3. flatpress · flatpress 2023-03-02 medium5.4 CVE-2023-1107 Cross-site Scripting (XSS) - Stored in GitHub repository flatpressblog/flatpress prior to 1.3. flatpress · flatpress 2023-03-02 medium6.1 CVE-2023-1106 Cross-site Scripting (XSS) - Reflected in GitHub repository flatpressblog/flatpress prior to 1.3. flatpress · flatpress 2023-03-02 high8.1 CVE-2023-1105 External Control of File Name or Path in GitHub repository flatpressblog/flatpress prior to 1.3. flatpress · flatpress 2023-03-01 medium5.4 CVE-2023-1104 Cross-site Scripting (XSS) - Stored in GitHub repository flatpressblog/flatpress prior to 1.3. flatpress · flatpress 2023-03-01 critical9.8 CVE-2023-0947 Path Traversal in GitHub repository flatpressblog/flatpress prior to 1.3. flatpress · flatpress 2023-02-22 low2.4 CVE-2022-4822 A vulnerability, which was classified as problematic, has been found in FlatPress. flatpress · flatpress 2022-12-28 low2.4 CVE-2022-4821 A vulnerability classified as problematic was found in FlatPress. flatpress · flatpress 2022-12-28 low3.5 CVE-2022-4820 A vulnerability classified as problematic has been found in FlatPress. flatpress · flatpress 2022-12-28 low3.5 CVE-2022-4755 A vulnerability was found in FlatPress and classified as problematic. flatpress · flatpress 2022-12-27 medium5.5 CVE-2022-4748 A vulnerability was found in FlatPress. flatpress · flatpress 2022-12-27 medium5.4 CVE-2022-4605 Cross-site Scripting (XSS) - Stored in GitHub repository flatpressblog/flatpress prior to 1.3. flatpress · flatpress 2022-12-18 critical9.8 CVE-2022-4606 PHP Remote File Inclusion in GitHub repository flatpressblog/flatpress prior to 1.3. flatpress · flatpress 2022-12-18 medium5.4 CVE-2022-40047 Flatpress v1.2.1 was discovered to contain a reflected cross-site scripting (XSS) vulnerability via the page parameter at /flatpress/admin.php. flatpress · flatpress 2022-10-11 high7.2 CVE-2022-40048 Flatpress v1.2.1 was discovered to contain a remote code execution (RCE) vulnerability in the Upload File function. flatpress · flatpress 2022-09-29

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.