Critical security advisoryCriticalFlagged by our vulnerability database: PHP2Shell is on CISA’s exploited list. Most WordPress hosting runs PHP. See if your site is affectedFlagged by our vulnerability database: PHP2Shell is being exploited. DetailsExploited: PHP2Shell. Check your site
HuttenlocherTechnologies
Updated 1 h ago

Vulnerability database

Every flaw the U.S. government’s cybersecurity agency (CISA) has confirmed attackers are using, plus the new WordPress plugin and theme bugs published each day, sorted by what they mean for a small business. We refresh it twice a day. If you see something your website or office runs, tell us.

1,764exploited flaws on CISA’s list
35added in the last 30 days
474new WordPress flaws this week
390,714entries in the database

8 results

  • Apr 15, 2026Luanti 5 before 5.15.2, when LuaJIT is used, allows a Lua sandbox escape via a crafted mod.CVE-2026-40959 · Other software · Luanti · reported by MITRECritical 9.3

    Luanti 5 before 5.15.2, when LuaJIT is used, allows a Lua sandbox escape via a crafted mod.

    Product
    Luanti
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Apr 6, 2026Lupa integrates the runtimes of Lua or LuaJIT2 into CPython.CVE-2026-34444 · Other software · scoder · reported by GitHubHigh 7.9

    Lupa integrates the runtimes of Lua or LuaJIT2 into CPython. In 2.6 and earlier, attribute_filter is not consistently applied when attributes are accessed through built-in functions like getattr and setattr. This allows an attacker to bypass the intended restrictions and eventually achieve arbitrary code execution.

    Product
    lupa
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 7, 2025LuaJIT through 2.1 and OpenRusty luajit2 before v2.1-20240314 have an out-of-bounds read in the stack-overflow handler in lj_state.c.CVE-2024-25178 · Other software · Luajit · reported by MITRECritical 9.1

    LuaJIT through 2.1 and OpenRusty luajit2 before v2.1-20240314 have an out-of-bounds read in the stack-overflow handler in lj_state.c.

    Product
    Luajit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 7, 2025LuaJIT through 2.1 and OpenRusty luajit2 before v2.1-20240314 have an unsinking of IR_FSTORE for NULL metatable, which leads to Denial of Service (DoS).CVE-2024-25177 · Other software · Luajit · reported by MITREHigh 7.5

    LuaJIT through 2.1 and OpenRusty luajit2 before v2.1-20240314 have an unsinking of IR_FSTORE for NULL metatable, which leads to Denial of Service (DoS).

    Product
    Luajit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 7, 2025LuaJIT through 2.1 and OpenRusty luajit2 before v2.1-20240626 have a stack-buffer-overflow in lj_strfmt_wfnum in lj_strfmt_num.c.CVE-2024-25176 · Other software · Luajit · reported by MITRECritical 9.8

    LuaJIT through 2.1 and OpenRusty luajit2 before v2.1-20240626 have a stack-buffer-overflow in lj_strfmt_wfnum in lj_strfmt_num.c.

    Product
    Luajit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 17, 2020LuaJIT through 2.1.0-beta3 has an out-of-bounds read in lj_err_run in lj_err.c.CVE-2020-24372 · Other software · Luajit · reported by MITREHigh 7.5

    LuaJIT through 2.1.0-beta3 has an out-of-bounds read in lj_err_run in lj_err.c.

    Product
    Luajit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Jul 21, 2020LuaJit through 2.1.0-beta3 has an out-of-bounds read because __gc handler frame traversal is mishandled.CVE-2020-15890 · Other software · Luajit · reported by MITREHigh 7.5

    LuaJit through 2.1.0-beta3 has an out-of-bounds read because __gc handler frame traversal is mishandled.

    Product
    Luajit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Nov 29, 2019In LuaJIT through 2.0.5, as used in Moonjit before 2.1.2 and other products, debug.getinfo has a type confusion issue that leads to arbitrary memory write or reCVE-2019-19391 · Other software · Luajit · reported by MITRECritical 9.1

    In LuaJIT through 2.0.5, as used in Moonjit before 2.1.2 and other products, debug.getinfo has a type confusion issue that leads to arbitrary memory write or read operations, because certain cases involving valid stack levels and > options are mishandled. NOTE: The LuaJIT project owner states that the debug libary is unsafe by definition and that this is not a vulnerability. When LuaJIT was originally developed, the expectation was that the entire debug library had no security guarantees and thus it made no sense to assign CVEs. However, not all users of later LuaJIT derivatives share this perspective

    Product
    Luajit
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.

Where this comes from: the exploited list is CISA’s Known Exploited Vulnerabilities catalog. Everything else is the whole National Vulnerability Database, where each record is published by the team that found the bug (Wordfence, Patchstack, WPScan, the vendors themselves and others); we show who. Exploit odds are FIRST’s EPSS, updated daily. Titles and categories are ours, so check the linked record before acting on a detail. For a write-up of the big ones, see our advisories. Every vendor, and every WordPress plugin and theme with a recorded flaw, also has its own page. All of it is free to reuse as JSON, CSV or RSS.

Weekly security brief

The flaws that hit local websites, every Friday.

One short email: what got exploited this week, which WordPress plugins broke, and what to check. Unsubscribe in one click.

Get in touch

Tell us what you're building.

A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.

01The person who'll do the work writes back
02A short call, then a written plan with the price
03Nothing starts until you say yes
04Hacked or down right now? Call, and we pick up the same day
843-331-6339

Not ready to talk yet? Run the free website check and see what Google sees.

What do you need?
Build
Grow
Protect
Urgent

No newsletter, no sales sequence. Just a reply.