Vulnerability database · updated every 15 minutes

New vulnerabilities in the software websites run.

CVEs and security advisories for WordPress, its plugins and themes, npm, PyPI and the servers behind websites, merged from NVD, the CVE Program, GitHub, OSV.dev and WPVulnerability, with CISA's list of the ones attackers exploit.

Free · right away or once a day · unsubscribe in one click
Tracked
55,391
Published in 7 days
1,887
Critical in 30 days
489
Actively exploited
542
Clear filters

Results for “Node.js”

291 vulnerabilities
  1. Critical 9.8

    CVE-2022-41878 · Parse Server

    Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. In versions prior to 5.3.2 or 4.10.19, keywords that are specified in the Parse Server option `requestKeywordDenylist` can be injected via Cloud Code Webhooks or Triggers. This will result in the keyword being saved to the database, bypassing the `requestKeywordDenylist` option. This issue is…

    Published 10 Nov 2022 · Fixed in 4.10.19, 5.3.2 · NVD
  2. Critical 9.8

    CVE-2022-41879 · Parse Server

    Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. In versions prior to 5.3.3 or 4.10.20, a compromised Parse Server Cloud Code Webhook target endpoint allows an attacker to use prototype pollution to bypass the Parse Server `requestKeywordDenylist` option. This issue has been patched in versions 5.3.3 and 4.10.20. There are no known…

    Published 10 Nov 2022 · Fixed in 4.10.20, 5.3.3 · NVD
  3. Critical 9.8

    CVE-2022-39396 · Parse Server

    Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Versions prior to 4.10.18, and prior to 5.3.1 on the 5.X branch, are vulnerable to Remote Code Execution via prototype pollution. An attacker can use this prototype pollution sink to trigger a remote code execution through the MongoDB BSON parser. This issue is patched in version 5.3.1 and in…

    Published 10 Nov 2022 · Fixed in 4.10.18, 5.3.1 · NVD
  4. High 7.5

    CVE-2022-3786 · Node.js, OpenSSL

    A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed a malicious certificate or for an application to continue certificate verification despite failure to construct a path to a trusted issuer. An attacker can craft a malicious…

    Published 1 Nov 2022 · Fixed in 3.0.7, 18.11.0 · NVD
  5. High 7.5

    CVE-2022-3602 · Node.js, OpenSSL

    A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Note that this occurs after certificate chain signature verification and requires either a CA to have signed the malicious certificate or for the application to continue certificate verification despite failure to construct a path to a trusted issuer. An attacker can craft a malicious…

    Published 1 Nov 2022 · Fixed in 3.0.7, 18.11.0 · NVD
  6. High 7.5

    CVE-2022-39313 · Parse Server

    Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Versions prior to 4.10.17, and prior to 5.2.8 on the 5.x branch, crash when a file download request is received with an invalid byte range, resulting in a Denial of Service. This issue has been patched in versions 4.10.17, and 5.2.8. There are no known workarounds.

    Published 24 Oct 2022 · Fixed in 4.10.17, 5.2.8 · NVD
  7. Low 3.7

    CVE-2022-39231 · Parse Server

    Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. In versions prior to 4.10.16, or from 5.0.0 to 5.2.6, validation of the authentication adapter app ID for _Facebook_ and _Spotify_ may be circumvented. Configurations which allow users to authenticate using the Parse Server authentication adapter where `appIds` is set as a string instead of an…

    Published 23 Sept 2022 · Fixed in 4.10.16, 5.2.7 · NVD
  8. Low 3.1

    CVE-2022-39225 · Parse Server

    Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. In versions prior to 4.10.15, or 5.0.0 and above prior to 5.2.6, a user can write to the session object of another user if the session object ID is known. For example, an attacker can assign the session object to their own user by writing to the `user` field and then read any custom fields of…

    Published 23 Sept 2022 · Fixed in 4.10.15, 5.2.6 · NVD
  9. High 7.5

    CVE-2022-36079 · Parse Server

    Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Internal fields (keys used internally by Parse Server, prefixed by `_`) and protected fields (user defined) can be used as query constraints. Internal and protected fields are removed by Parse Server and are only returned to the client using a valid master key. However, using query…

    Published 7 Sept 2022 · Fixed in 4.10.14, 5.2.5 · NVD
  10. High 7.3

    CVE-2022-32223 · Node.js

    Node.js is vulnerable to Hijack Execution Flow: DLL Hijacking under certain conditions on Windows platforms.This vulnerability can be exploited if the victim has the following dependencies on a Windows machine:* OpenSSL has been installed and “C:\Program Files\Common Files\SSL\openssl.cnf” exists.Whenever the above conditions are present, `node.exe` will search for `providers.dll` in the current…

    Published 14 Jul 2022 · Fixed in 14.20.0, 16.16.0, 18.0.5 · NVD
  11. Medium 5.3

    CVE-2022-32222 · Node.js

    A cryptographic vulnerability exists on Node.js on linux in versions of 18.x prior to 18.40.0 which allowed a default path for openssl.cnf that might be accessible under some circumstances to a non-admin user instead of /etc/ssl as was the case in versions prior to the upgrade to OpenSSL 3.

    Published 14 Jul 2022 · Fixed in 18.5.0 · NVD
  12. Medium 6.5

    CVE-2022-32215 · Node.js

    The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not correctly handle multi-line Transfer-Encoding headers. This can lead to HTTP Request Smuggling (HRS).

    Published 14 Jul 2022 · Fixed in 14.20.0, 16.16.0, 18.5.0 · NVD
  13. Medium 6.5

    CVE-2022-32214 · Node.js

    The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not strictly use the CRLF sequence to delimit HTTP requests. This can lead to HTTP Request Smuggling (HRS).

    Published 14 Jul 2022 · Fixed in 14.20.0, 16.16.0, 18.5.0 · NVD
  14. Medium 6.5

    CVE-2022-32213 · Node.js

    The llhttp parser <v14.20.1, <v16.17.1 and <v18.9.1 in the http module in Node.js does not correctly parse and validate Transfer-Encoding headers and can lead to HTTP Request Smuggling (HRS).

    Published 14 Jul 2022 · Fixed in 14.20.1, 16.17.1, 18.9.1 · NVD
  15. High 8.1

    CVE-2022-32212 · Node.js

    A OS Command Injection vulnerability exists in Node.js versions <14.20.0, <16.20.0, <18.5.0 due to an insufficient IsAllowedHost check that can easily be bypassed because IsIPAddress does not properly check if an IP address is invalid before making DBS requests allowing rebinding attacks.

    Published 14 Jul 2022 · Fixed in 14.20.1, 16.17.1, 18.5.0 · NVD
  16. High 8.2

    CVE-2022-31112 · Parse Server

    Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. In affected versions parse Server LiveQuery does not remove protected fields in classes, passing them to the client. The LiveQueryController now removes protected fields from the client response. Users are advised to upgrade. Users unable t upgrade should use `Parse.Cloud.afterLiveQueryEvent`…

    Published 30 Jun 2022 · Fixed in 4.10.13, 5.2.4 · NVD
  17. High 7.5

    CVE-2022-31089 · Parse Server

    Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. In affected versions certain types of invalid files requests are not handled properly and can crash the server. If you are running multiple Parse Server instances in a cluster, the availability impact may be low; if you are running Parse Server as single instance without redundancy, the…

    Published 27 Jun 2022 · Fixed in 4.10.12, 5.2.3 · NVD
  18. High 7.5

    CVE-2022-31083 · Parse Server

    Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 4.10.11 and 5.2.2, the certificate in the Parse Server Apple Game Center auth adapter not validated. As a result, authentication could potentially be bypassed by making a fake certificate accessible via certain Apple domains and providing the URL to that certificate in an…

    Published 17 Jun 2022 · Fixed in 4.10.11, 5.2.2 · NVD
  19. High 7.5

    CVE-2022-0778 · MariaDB, Node.js, OpenSSL

    The BN_mod_sqrt() function, which computes a modular square root, contains a bug that can cause it to loop forever for non-prime moduli. Internally this function is used when parsing certificates that contain elliptic curve public keys in compressed form or explicit elliptic curve parameters with a base point encoded in compressed form. It is possible to trigger the infinite loop by crafting a…

    Published 15 Mar 2022 · Fixed in 14.19.1, 16.14.2, 17.7.2 · NVD
  20. High 8.2

    CVE-2022-21824 · Node.js, MySQL

    Due to the formatting logic of the "console.table()" function it was not safe to allow user controlled input to be passed to the "properties" parameter while simultaneously passing a plain object with at least one property as the first parameter, which could be "__proto__". The prototype pollution has very limited control, in that it only allows an empty string to be assigned to numerical keys…

    Published 24 Feb 2022 · Fixed in 14.18.3, 16.13.2, 17.3.1 · NVD
  21. Medium 5.3

    CVE-2021-44533 · Node.js, MySQL

    Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 did not handle multi-value Relative Distinguished Names correctly. Attackers could craft certificate subjects containing a single-value Relative Distinguished Name that would be interpreted as a multi-value Relative Distinguished Name, for example, in order to inject a Common Name that would allow bypassing the certificate subject…

    Published 24 Feb 2022 · Fixed in 14.18.3, 16.13.2, 17.3.1 · NVD
  22. Medium 5.3

    CVE-2021-44532 · Node.js, MySQL

    Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 converts SANs (Subject Alternative Names) to a string format. It uses this string to check peer certificates against hostnames when validating connections. The string format was subject to an injection vulnerability when name constraints were used within a certificate chain, allowing the bypass of these name constraints.Versions of Node.js…

    Published 24 Feb 2022 · Fixed in 14.18.3, 16.13.2, 17.3.1 · NVD
  23. High 7.4

    CVE-2021-44531 · Node.js, MySQL

    Accepting arbitrary Subject Alternative Name (SAN) types, unless a PKI is specifically defined to use a particular SAN type, can result in bypassing name-constrained intermediates. Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 was accepting URI SAN types, which PKIs are often not defined to use. Additionally, when a protocol allows URI SANs, Node.js did not match the URI…

    Published 24 Feb 2022 · Fixed in 14.18.3, 16.13.2, 17.3.1 · NVD
  24. High 7.5

    CVE-2021-4044 · Node.js, OpenSSL

    Internally libssl in OpenSSL calls X509_verify_cert() on the client side to verify a certificate supplied by a server. That function may return a negative return value to indicate an internal error (for example out of memory). Such a negative return value is mishandled by OpenSSL and will cause an IO function (such as SSL_connect() or SSL_do_handshake()) to not indicate success and a subsequent…

    Published 14 Dec 2021 · Fixed in 1.0.2, 17.3.0 · NVD
  25. Medium 5.6

    CVE-2021-3672 · c-ares, Node.js

    A flaw was found in c-ares library, where a missing input validation check of host names returned by DNS (Domain Name Servers) can lead to output of wrong hostnames which might potentially lead to Domain Hijacking. The highest threat from this vulnerability is to confidentiality and integrity as well as system availability.

    Published 23 Nov 2021 · Fixed in 12.22.5, 14.17.5, 16.6.2 · NVD
  26. Critical 9.8

    CVE-2021-22930 · Node.js

    Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to a use after free attack where an attacker might be able to exploit the memory corruption, to change process behavior.

    Published 7 Oct 2021 · Fixed in 12.22.4, 14.17.4, 16.6.0 · NVD
  27. High 7.5

    CVE-2021-41109 · Parse Server

    Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to version 4.10.4, for regular (non-LiveQuery) queries, the session token is removed from the response, but for LiveQuery payloads it is currently not. If a user has a LiveQuery subscription on the `Parse.User` class, all session tokens created during user sign-ups will be broadcast as…

    Published 30 Sept 2021 · Fixed in 4.10.4 · NVD
  28. High 7.2

    CVE-2021-39192 · Ghost

    Ghost is a Node.js content management system. An error in the implementation of the limits service between versions 4.0.0 and 4.9.4 allows all authenticated users (including contributors) to view admin-level API keys via the integrations API endpoint, leading to a privilege escalation vulnerability. This issue is patched in Ghost version 4.10.0. As a workaround, disable all non-Administrator…

    Published 3 Sept 2021 · Fixed in 4.10.0 · NVD
  29. High 7.5

    CVE-2021-39187 · Parse Server

    Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to version 4.10.3, Parse Server crashes when if a query request contains an invalid value for the `explain` option. This is due to a bug in the MongoDB Node.js driver which throws an exception that Parse Server cannot catch. There is a patch for this issue in version 4.10.3. No…

    Published 2 Sept 2021 · Fixed in 4.10.3 · NVD
  30. Medium 6.5

    CVE-2021-39138 · Parse Server

    Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Developers can use the REST API to signup users and also allow users to login anonymously. Prior to version 4.5.1, when an anonymous user is first signed up using REST, the server creates session incorrectly. Particularly, the `authProvider` field in `_Session` class under `createdWith` shows…

    Published 19 Aug 2021 · Fixed in 4.5.1 · NVD
  31. High 7.5

    CVE-2021-22940 · Node.js

    Node.js before 16.6.1, 14.17.5, and 12.22.5 is vulnerable to a use after free attack where an attacker might be able to exploit the memory corruption, to change process behavior.

    Published 16 Aug 2021 · Fixed in 12.22.5, 14.17.5, 16.6.2 · NVD
  32. Medium 5.3

    CVE-2021-22939 · Node.js

    If the Node.js https API was used incorrectly and "undefined" was in passed for the "rejectUnauthorized" parameter, no error was returned and connections to servers with an expired certificate would have been accepted.

    Published 16 Aug 2021 · Fixed in 12.22.5, 14.17.5, 16.6.2 · NVD
  33. Critical 9.8

    CVE-2021-22931 · Node.js

    Node.js before 16.6.0, 14.17.4, and 12.22.4 is vulnerable to Remote Code Execution, XSS, Application crashes due to missing input validation of host names returned by Domain Name Servers in Node.js dns library which can lead to output of wrong hostnames (leading to Domain Hijacking) and injection vulnerabilities in applications using the library.

    Published 16 Aug 2021 · Fixed in 12.22.5, 14.17.5, 16.6.2 · NVD
  34. High 7.8

    CVE-2021-22921 · Node.js

    Node.js before 16.4.1, 14.17.2, and 12.22.2 is vulnerable to local privilege escalation attacks under certain conditions on Windows platforms. More specifically, improper configuration of permissions in the installation directory allows an attacker to perform two different escalation attacks: PATH and DLL hijacking.

    Published 12 Jul 2021 · Fixed in 12.22.2, 14.17.2, 16.4.1 · NVD
  35. Medium 5.3

    CVE-2021-22918 · Node.js

    Node.js before 16.4.1, 14.17.2, 12.22.2 is vulnerable to an out-of-bounds read when uv__idna_toascii() is used to convert strings to ASCII. The pointer p is read and increased without checking whether it is beyond pe, with the latter holding a pointer to the end of the buffer. This can lead to information disclosures or crashes. This function can be triggered via uv_getaddrinfo().

    Published 12 Jul 2021 · Fixed in 12.22.2, 14.17.2, 16.4.1 · NVD
  36. Medium 6.8

    CVE-2021-29484 · Ghost

    Ghost is a Node.js CMS. An unused endpoint added during the development of 4.0.0 has left sites vulnerable to untrusted users gaining access to Ghost Admin. Attackers can gain access by getting logged in users to click a link containing malicious code. Users do not need to enter credentials and may not know they've visited a malicious site. Ghost(Pro) has already been patched. We can find no…

    Published 29 Apr 2021 · Fixed in 4.3.3 · NVD
  37. High 7.4

    CVE-2021-3450 · Node.js, OpenSSL, MySQL and 2 more

    The X509_V_FLAG_X509_STRICT flag enables additional security checks of the certificates present in a certificate chain. It is not set by default. Starting from OpenSSL version 1.1.1h a check to disallow certificates in the chain that have explicitly encoded elliptic curve parameters was added as an additional strict check. An error in the implementation of this check meant that the result of a…

    Published 25 Mar 2021 · Fixed in 12.22.1, 14.16.1, 15.14.0 · NVD
  38. Medium 5.9

    CVE-2021-3449 · Node.js, OpenSSL, MySQL and 1 more

    An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client. If a TLSv1.2 renegotiation ClientHello omits the signature_algorithms extension (where it was present in the initial ClientHello), but includes a signature_algorithms_cert extension then a NULL pointer dereference will result, leading to a crash and a denial of service attack. A server…

    Published 25 Mar 2021 · Fixed in 12.22.1, 14.16.1, 15.14.0 · NVD
  39. High 7.5

    CVE-2021-22884 · Node.js

    Node.js before 10.24.0, 12.21.0, 14.16.0, and 15.10.0 is vulnerable to DNS rebinding attacks as the whitelist includes “localhost6”. When “localhost6” is not present in /etc/hosts, it is just an ordinary domain that is resolved via DNS, i.e., over network. If the attacker controls the victim's DNS server or can spoof its responses, the DNS rebinding protection can be bypassed by using the…

    Published 3 Mar 2021 · Fixed in 12.21.0, 14.16.0, 15.10.0 · NVD
  40. High 7.5

    CVE-2021-22883 · Node.js

    Node.js before 10.24.0, 12.21.0, 14.16.0, and 15.10.0 is vulnerable to a denial of service attack when too many connection attempts with an 'unknownProtocol' are established. This leads to a leak of file descriptors. If a file descriptor limit is configured on the system, then the server is unable to accept new connections and prevent the process also from opening, e.g. a file. If no file…

    Published 3 Mar 2021 · Fixed in 12.21.0, 14.16.0, 15.10.0 · NVD
  41. High 7.5

    CVE-2021-23840 · Node.js, OpenSSL, MySQL

    Calls to EVP_CipherUpdate, EVP_EncryptUpdate and EVP_DecryptUpdate may overflow the output length argument in some cases where the input length is close to the maximum permissable length for an integer on the platform. In such cases the return value from the function call will be 1 (indicating success), but the output length value will be negative. This could cause applications to behave…

    Published 16 Feb 2021 · Fixed in 10.24.0, 12.21.0, 15.10.0 · NVD
  42. Medium 6.5

    CVE-2020-8287 · Node.js

    Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 allow two copies of a header field in an HTTP request (for example, two Transfer-Encoding header fields). In this case, Node.js identifies the first header field and ignores the second. This can lead to HTTP Request Smuggling.

    Published 6 Jan 2021 · Fixed in 12.20.1, 14.15.4, 15.5.1 · NVD
  43. High 8.1

    CVE-2020-8265 · Node.js

    Node.js versions before 10.23.1, 12.20.1, 14.15.4, 15.5.1 are vulnerable to a use-after-free bug in its TLS implementation. When writing to a TLS enabled socket, node::StreamBase::Write calls node::TLSWrap::DoWrite with a freshly allocated WriteWrap object as first argument. If the DoWrite method does not return an error, this object is passed back to the caller as part of a StreamWriteResult…

    Published 6 Jan 2021 · Fixed in 12.20.1, 14.15.4, 15.5.1 · NVD
  44. Medium 6.5

    CVE-2020-26288 · Parse Server

    Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. It is an npm package "parse-server". In Parse Server before version 4.5.0, user passwords involved in LDAP authentication are stored in cleartext. This is fixed in version 4.5.0 by stripping password after authentication to prevent cleartext password storage.

    Published 30 Dec 2020 · Fixed in 4.5.0 · NVD
  45. Medium 5.9

    CVE-2020-1971 · Node.js, OpenSSL, MySQL

    The X.509 GeneralName type is a generic type for representing different types of names. One of those name types is known as EDIPartyName. OpenSSL provides a function GENERAL_NAME_cmp which compares different instances of a GENERAL_NAME to see if they are equal or not. This function behaves incorrectly when both GENERAL_NAMEs contain an EDIPARTYNAME. A NULL pointer dereference and a crash may…

    Published 8 Dec 2020 · Fixed in 12.20.1, 14.15.4, 15.5.0 · NVD
  46. Medium 6.5

    CVE-2018-21270 · Node.js

    Versions less than 0.0.6 of the Node.js stringstream module are vulnerable to an out-of-bounds read because of allocation of uninitialized buffers when a number is passed in the input stream (when using Node.js 4.x).

    Published 3 Dec 2020 · Fixed in 0.0.6 · NVD
  47. High 7.5

    CVE-2020-8277 · c-ares, Node.js

    A Node.js application that allows an attacker to trigger a DNS request for a host of their choice could trigger a Denial of Service in versions < 15.2.1, < 14.15.1, and < 12.19.1 by getting the application to resolve a DNS record with a larger number of responses. This is fixed in 15.2.1, 14.15.1, and 12.19.1.

    Published 19 Nov 2020 · Fixed in 12.19.1, 14.15.1, 15.2.1 · NVD
  48. High 7.8

    CVE-2020-8252 · Node.js

    The implementation of realpath in libuv < 10.22.1, < 12.18.4, and < 14.9.0 used within Node.js incorrectly determined the buffer size which can result in a buffer overflow if the resolved path is longer than 256 bytes.

    Published 18 Sept 2020 · Fixed in 10.22.1, 12.18.4, 14.9.0 · NVD
  49. High 7.5

    CVE-2020-8251 · Node.js

    Node.js < 14.11.0 is vulnerable to HTTP denial of service (DoS) attacks based on delayed requests submission which can make the server unable to accept new connections.

    Published 18 Sept 2020 · Fixed in 14.11.0 · NVD
  50. High 7.4

    CVE-2020-8201 · Node.js

    Node.js < 12.18.4 and < 14.11 can be exploited to perform HTTP desync attacks and deliver malicious payloads to unsuspecting users. The payloads can be crafted by an attacker to hijack user sessions, poison cookies, perform clickjacking, and a multitude of other attacks depending on the architecture of the underlying system. The attack was possible due to a bug in processing of carrier-return…

    Published 18 Sept 2020 · Fixed in 12.18.4, 14.11.0 · NVD

Where it comes from

The list holds every advisory UpHeron reads for the software it watches: WordPress and every plugin and theme its plugin reports, the packages in monitored repositories and manifests, and the servers and frameworks found on monitored websites. One vulnerability from several sources is one entry, under its CVE.

  • NVD, the US National Vulnerability Database. This product uses the NVD API but is not endorsed or certified by the NVD.
  • New and changed records of the CVE Program, read every 15 minutes, so a rating or fix added after a CVE is published reaches the list, and its alerts, within the hour. CVE content © 1999–2026 The MITRE Corporation, used under the CVE terms of use; CVE® is a registered trademark of The MITRE Corporation.
  • OSV.dev, with the GitHub Advisory Database (CC BY 4.0).
  • WPVulnerability (CC0) for WordPress plugins and themes, and WordPress's own security advisories.
  • Node.js's own security release posts, read every 15 minutes, which name its vulnerabilities the day they are fixed, days before their CVE records.
  • The security advisories projects publish on GitHub, and the CVEs libraries such as Brotli name in their release notes, which also count for the runtimes that bundle them.
  • CISA's Known Exploited Vulnerabilities catalog.

Each day's new ones, grouped, and every critical one as soon as we find it: on the blog.

Run WordPress? The UpHeron plugin alerts you the day one of these affects your own site.