Critical security advisoryCriticalFlagged by our vulnerability database: A flaw in WordPress’s own updater is being exploited. Sites need 7.1.4. See if your site is affectedFlagged by our vulnerability database: WordPress updater flaw is being exploited. DetailsExploited: WordPress 7.1.4. Check your site
HuttenlocherTechnologies
Updated 7 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,781exploited flaws on CISA’s list
33added in the last 30 days
393new WordPress flaws this week
399,326entries in the database

399,326 results · page 850 of 7987

  • Aug 24, 2026Multiple DrayTek VigorSwitch models contain a buffer overflow vulnerability in the switch_lan_gvrp function.CVE-2026-71938 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.6

    Multiple DrayTek VigorSwitch models contain a buffer overflow vulnerability in the switch_lan_gvrp function. The vulnerability is caused by unsafe copying of the portList field into an undersized buffer. A remote attacker can trigger this vulnerability via crafted input, causing a denial of service or potentially executing arbitrary commands. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorSwitch G2540xs
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorSwitch models contain a buffer overflow vulnerability in the poe_schedule_profile function.CVE-2026-71937 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.6

    Multiple DrayTek VigorSwitch models contain a buffer overflow vulnerability in the poe_schedule_profile function. The vulnerability is caused by repeated concatenation of the start_date, start_time, duration_time, how_often, weekdays, monthly_date, and cycle_duration fields into small fixed-size buffers without proper length checks. A remote attacker can trigger this vulnerability via crafted input, causing a denial of service or potentially executing arbitrary commands. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorSwitch G2540xs
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorSwitch models contain a buffer overflow vulnerability in the sysreboot function.CVE-2026-71936 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.6

    Multiple DrayTek VigorSwitch models contain a buffer overflow vulnerability in the sysreboot function. The vulnerability is caused by unsafe concatenation of split valueN data into a fixed-size buffer. A remote attacker can trigger this vulnerability via crafted input, causing a denial of service or potentially executing arbitrary commands. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorSwitch G2540xs
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorSwitch models contain a buffer overflow vulnerability in the webBackupAction function.CVE-2026-71935 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.6

    Multiple DrayTek VigorSwitch models contain a buffer overflow vulnerability in the webBackupAction function. The vulnerability is caused by repeated string concatenation of the pathN, valueN, key, and option fields into fixed-size stack buffers without total length checks. A remote attacker can trigger this vulnerability via crafted input, causing a denial of service or potentially executing arbitrary commands. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorSwitch G2540xs
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorSwitch models contain a buffer overflow vulnerability in the pingtrace function.CVE-2026-71934 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.6

    Multiple DrayTek VigorSwitch models contain a buffer overflow vulnerability in the pingtrace function. The vulnerability is caused by missing length checks when the host, count, and interval fields are concatenated into a fixed-size buffer. A remote attacker can trigger this vulnerability via crafted input, causing a denial of service or potentially executing arbitrary commands. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorSwitch G2540xs
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorSwitch models contain unauthorized operation vulnerabilities in multiple syslog functions.CVE-2026-71933 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.8

    Multiple DrayTek VigorSwitch models contain unauthorized operation vulnerabilities in multiple syslog functions. The vulnerability is caused by missing authorization checks. A remote attacker can trigger these vulnerabilities via crafted requests to modify configuration, restart services, save startup configuration, or clear logs.

    Product
    VigorSwitch G2540xs
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorSwitch models contain a directory traversal vulnerability in the getSyslogFile function.CVE-2026-71932 · Network & remote access · DrayTek Corporation · reported by VulnCheckMedium 6.9

    Multiple DrayTek VigorSwitch models contain a directory traversal vulnerability in the getSyslogFile function. The vulnerability is caused by insufficient validation of the option field. A remote attacker can trigger this vulnerability via crafted input containing path traversal sequences to access arbitrary files on the device. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorSwitch G2540xs
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the tftp_upgrade function.CVE-2026-71931 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.6

    Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the tftp_upgrade function. The vulnerability is caused by insufficient filtering before the filename field is concatenated into a command. A remote attacker can trigger this vulnerability via crafted input to execute arbitrary commands with root privileges. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorSwitch G2540xs
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the setTime function.CVE-2026-71930 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.6

    Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the setTime function. The vulnerability is caused by insufficient filtering of the username and password fields before command execution. A remote attacker can trigger this vulnerability via crafted input to execute arbitrary commands with root privileges. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorSwitch G2540xs
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the setDevProto function.CVE-2026-71929 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.6

    Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the setDevProto function. The vulnerability is caused by insufficient filtering of the username and password fields before command execution. A remote attacker can trigger this vulnerability via crafted input to execute arbitrary commands with root privileges. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorSwitch G2540xs
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the fdftDevice function.CVE-2026-71928 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.6

    Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the fdftDevice function. The vulnerability is caused by insufficient filtering of the username and password fields before command execution. A remote attacker can trigger this vulnerability via crafted input to execute arbitrary commands with root privileges. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorSwitch G2540xs
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the rebDevice function.CVE-2026-71927 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.6

    Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the rebDevice function. The vulnerability is caused by insufficient filtering of the username and password fields before command execution. A remote attacker can trigger this vulnerability via crafted input to execute arbitrary commands with root privileges. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorSwitch G2540xs
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the setDevice function.CVE-2026-71926 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.6

    Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the setDevice function. The vulnerability is caused by insufficient sanitization of the username, password, and location fields before command execution. A remote attacker can trigger this vulnerability via crafted input to execute arbitrary commands with root privileges. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorSwitch G2540xs
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the getDetail function.CVE-2026-71925 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.6

    Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the getDetail function. The vulnerability is caused by insufficient filtering of the username and password fields before command execution. A remote attacker can trigger this vulnerability via crafted input to execute arbitrary commands with root privileges. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorSwitch G2540xs
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the getVid function.CVE-2026-71924 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.6

    Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the getVid function. The vulnerability is caused by insufficient filtering of the username and password fields before command execution. A remote attacker can trigger this vulnerability via crafted input to execute arbitrary commands with root privileges. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorSwitch G2540xs
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the auth_set function.CVE-2026-71923 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.6

    Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the auth_set function. The vulnerability is caused by insufficient filtering of the username and password fields before command execution. A remote attacker can trigger this vulnerability via crafted input to execute arbitrary commands with root privileges. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorSwitch G2540xs
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorSwitch models contain a pre-authentication null pointer dereference vulnerability in the setget.cgi interface.CVE-2026-71922 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.7

    Multiple DrayTek VigorSwitch models contain a pre-authentication null pointer dereference vulnerability in the setget.cgi interface. The vulnerability is caused by missing validation when the pass field is absent. A remote attacker can trigger this vulnerability via a crafted request to crash the service and cause a denial of service.

    Product
    VigorSwitch G2540xs
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorSwitch models contain a pre-authentication command injection vulnerability in the setget.cgi interface.CVE-2026-71921 · Network & remote access · DrayTek Corporation · reported by VulnCheckCritical 9.3

    Multiple DrayTek VigorSwitch models contain a pre-authentication command injection vulnerability in the setget.cgi interface. The vulnerability is caused by insufficient filtering of the pass field before command execution. A remote attacker can trigger this vulnerability via crafted input to execute arbitrary commands with root privileges.

    Product
    VigorSwitch G2540xs
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorSwitch models contain a null pointer dereference vulnerability in the formlogout function.CVE-2026-71920 · Network & remote access · DrayTek Corporation · reported by VulnCheckMedium 6.9

    Multiple DrayTek VigorSwitch models contain a null pointer dereference vulnerability in the formlogout function. The vulnerability is caused by missing checks for an empty or absent Cookie header before string handling. A remote attacker can trigger this vulnerability via a crafted request to crash the service and cause a denial of service. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorSwitch G2540xs
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the sysreboot function.CVE-2026-71919 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.6

    Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the sysreboot function. The vulnerability is caused by insufficient filtering of the config, act, pathN, and valueN fields before command execution. A remote attacker can trigger this vulnerability via crafted input to execute arbitrary commands with root privileges. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorSwitch G2540xs
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the webBackupAction function.CVE-2026-71918 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.6

    Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the webBackupAction function. The vulnerability is caused by insufficient filtering of the option, key, pw_encode, pathN, and valueN fields before command execution. A remote attacker can trigger this vulnerability via crafted input to execute arbitrary commands with root privileges. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorSwitch G2540xs
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the pingtrace function.CVE-2026-71917 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.6

    Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the pingtrace function. The vulnerability is caused by insufficient validation of the host field before command execution. A remote attacker can trigger this vulnerability via crafted input to execute arbitrary commands with root privileges. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorSwitch G2540xs
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the commandTable function.CVE-2026-71916 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.6

    Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the commandTable function. The vulnerability is caused by incomplete filtering of dangerous characters such as backticks, newline characters, and single quotes in the parameter field. A remote attacker can trigger this vulnerability via crafted input to execute arbitrary commands with root privileges. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorSwitch G2540xs
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the jsonstatus function.CVE-2026-71915 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.6

    Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the jsonstatus function. The vulnerability is caused by insufficient filtering of the usescript, usefile, and option fields before command execution. A remote attacker can trigger this vulnerability via crafted input to execute arbitrary commands with root privileges. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorSwitch G2540xs
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorAP models contain a command injection vulnerability in the dray_apm component.CVE-2026-71914 · Network & remote access · DrayTek Corporation · reported by VulnCheckCritical 9.3

    Multiple DrayTek VigorAP models contain a command injection vulnerability in the dray_apm component. The vulnerability is caused by insufficient validation of UDP message content after START_SPEED_TEST before command execution. A remote attacker can trigger this vulnerability via a crafted message to execute arbitrary commands with root privileges.

    Product
    VigorAP 918R
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorAP models contain a command injection vulnerability in the upload_settings.cgi interface.CVE-2026-71913 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.6

    Multiple DrayTek VigorAP models contain a command injection vulnerability in the upload_settings.cgi interface. The vulnerability is caused by insufficient filtering before the restorekey field is concatenated into a shell command. A remote attacker can trigger this vulnerability via crafted input to execute arbitrary commands with root privileges. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorAP 918R
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorAP models contain a buffer overflow vulnerability in the apautotest function.CVE-2026-71912 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.6

    Multiple DrayTek VigorAP models contain a buffer overflow vulnerability in the apautotest function. The vulnerability is caused by missing length checks during memory copy operations involving the CMD6 field. A remote attacker can trigger this vulnerability via crafted input, causing a denial of service or potentially executing arbitrary commands. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorAP 918R
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorAP models contain a buffer overflow vulnerability in the setLan function.CVE-2026-71911 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.6

    Multiple DrayTek VigorAP models contain a buffer overflow vulnerability in the setLan function. The vulnerability is caused by missing length checks during memory copy operations involving the lanVlanId0, lanIp, and lanNetmask fields. A remote attacker can trigger this vulnerability via crafted input, causing a denial of service or potentially executing arbitrary commands. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorAP 918R
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorAP models contain a command injection vulnerability in the apautotest function.CVE-2026-71910 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.6

    Multiple DrayTek VigorAP models contain a command injection vulnerability in the apautotest function. The vulnerability is caused by insufficient validation of the CMD0, CMD3, and CMD6 fields before command execution. A remote attacker can trigger this vulnerability via crafted input to execute arbitrary commands with root privileges. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorAP 918R
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorAP models contain a command injection vulnerability in the InquierTime function.CVE-2026-71909 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.6

    Multiple DrayTek VigorAP models contain a command injection vulnerability in the InquierTime function. The vulnerability is caused by insufficient filtering of the time field before command execution. A remote attacker can trigger this vulnerability via crafted input to execute arbitrary commands with root privileges. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorAP 918R
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorAP models contain a command injection vulnerability in the mesh_start_speed_test function.CVE-2026-71908 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.6

    Multiple DrayTek VigorAP models contain a command injection vulnerability in the mesh_start_speed_test function. The vulnerability is caused by insufficient sanitization of the meshdevice_index and meshdevice_ip fields before command execution. A remote attacker can trigger this vulnerability via crafted input to execute arbitrary commands with root privileges. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorAP 918R
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorAP models contain a command injection vulnerability in the setcamset function.CVE-2026-71907 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.6

    Multiple DrayTek VigorAP models contain a command injection vulnerability in the setcamset function. The vulnerability is caused by insufficient filtering of the selectSlaves field before command execution. A remote attacker can trigger this vulnerability via crafted input to execute arbitrary commands with root privileges. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorAP 918R
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorAP models contain a command injection vulnerability in the setLan function.CVE-2026-71906 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.6

    Multiple DrayTek VigorAP models contain a command injection vulnerability in the setLan function. The vulnerability is caused by insufficient validation of the lanIp and lanNetmask fields before command execution. A remote attacker can trigger this vulnerability via crafted input to execute arbitrary commands with root privileges. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorAP 918R
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorAP models contain a command injection vulnerability in the ExportSettings function.CVE-2026-71905 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.6

    Multiple DrayTek VigorAP models contain a command injection vulnerability in the ExportSettings function. The vulnerability is caused by insufficient filtering of the backupkey, backuptype, and realtime fields before command execution. A remote attacker can trigger this vulnerability via crafted input to execute arbitrary commands with root privileges. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorAP 918R
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Multiple DrayTek VigorAP models contain a command injection vulnerability in the tr069TestInform function.CVE-2026-71904 · Network & remote access · DrayTek Corporation · reported by VulnCheckHigh 8.6

    Multiple DrayTek VigorAP models contain a command injection vulnerability in the tr069TestInform function. The vulnerability is caused by insufficient filtering of dangerous characters before the event_code field is concatenated into a system command. A remote attacker can trigger this vulnerability via crafted input to execute arbitrary commands with root privileges. Exploitation requires valid administrative credentials for the device's web management interface.

    Product
    VigorAP 918R
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Improper neutralization of input during web page generation ('cross-site scripting') vulnerability in Johnson Controls Metasys 14 and Johnson Controls Metasys 1CVE-2026-34491 · Other software · Johnson Controls · reported by productsecurity@jci.comMedium 6.1

    Improper neutralization of input during web page generation ('cross-site scripting') vulnerability in Johnson Controls Metasys 14 and Johnson Controls Metasys 15 allows Cross Site Scripting. This issue affects Metasys 14: before 14.1.5; Metasys 15: before 15.0.1.

    Product
    Metasys 14
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026An authenticated command injection vulnerability in TP-Link Archer BE800 V1 allows an attacker with administrative access to execute arbitrary system commands wCVE-2026-16348 · Network & remote access · TP-Link Systems Inc. · reported by f23511db-6c3e-4e32-a477-6aa17d310630High 8.5

    An authenticated command injection vulnerability in TP-Link Archer BE800 V1 allows an attacker with administrative access to execute arbitrary system commands with root privileges by injecting shell metacharacters via a VPN connection.  Successful exploitation may enable persistent backdoors, credential theft, LAN reconnaissance, and router-assisted attacks against connected devices.

    Product
    Archer BE800 v1
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026The Hearing Access Service (HAS) GATT server in subsys/bluetooth/audio/has.c installs a connection-callback set unconditionally via BT_CONN_CB_DEFINE, so securiCVE-2026-13213 · Other software · zephyrproject · reported by vulnerabilities@zephyrproject.orgMedium 5.3

    The Hearing Access Service (HAS) GATT server in subsys/bluetooth/audio/has.c installs a connection-callback set unconditionally via BT_CONN_CB_DEFINE, so security_changed() runs for every connection that establishes security even before the application has called bt_has_register(). The service attribute pointers hearing_aid_features_attr, preset_control_point_attr, and active_preset_index_attr remain NULL until bt_has_register() resolves them and sets has.registered. With CONFIG_BT_SETTINGS, settings_set_cb() restores each bonded client's persisted context at boot and unconditionally sets context->flags to BONDED_CLIENT_INIT_FLAGS (non-zero). When a previously bonded peer reconnects and re-establishes security during the startup window before bt_has_register() has been called, security_changed() sees the non-zero flags and schedules notify_work_handler, which calls bt_gatt_is_subscribed() with a still-NULL attribute pointer. That triggers an assertion (__ASSERT(attr, ...) in bt_gatt_is_subscribed()), or a NULL dereference of attr->uuid when assertions are compiled out. The result is a remotely triggerable (Bluetooth, adjacent) crash of the HAS peripheral. Exploitation requires th

    Product
    zephyr
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026A flaw was found in the file-pcx plugin in GIMP, affecting 32-bit builds only.CVE-2026-78465 · Other software · GNOME · reported by Red HatHigh 7

    A flaw was found in the file-pcx plugin in GIMP, affecting 32-bit builds only. When processing a PCX image file, the plugin calculates memory allocation sizes based on the image dimensions and the number of color planes. If a crafted file sets the number of planes to 4 alongside sufficiently large dimensions, the calculation exceeds the 32-bit integer limit and overflows, resulting in an undersized heap-based buffer allocation. This integer overflow issue results in a heap-based buffer overflow when the plugin subsequently writes image data into the undersized buffer, causing memory corruption, potentially leading to arbitrary code execution or a denial of service.

    Product
    GIMP
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Improper input validation vulnerability in Apache Camel Undertow component.CVE-2026-78329 · Email & office · Apache Software Foundation · reported by security@apache.orgCritical 9.8

    Improper input validation vulnerability in Apache Camel Undertow component. This issue affects Apache Camel: from 4.11.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0. UndertowEndpoint defaulted its headerFilterStrategy field to the base HttpHeaderFilterStrategy and pushed that instance into the UndertowHttpBinding it creates lazily, overwriting the UndertowHeaderFilterStrategy that DefaultUndertowHttpBinding installs in its own constructor. Unless a deployment supplied a custom binding or an explicit headerFilterStrategy, the undertow-specific filtering therefore never executed on endpoint-configured routes: the strategy object was constructed and immediately replaced before it could be consulted. The consequence is that the legacy websocket. Exchange-header prefix was not filtered at the undertow transport boundary in either direction, so an undertow HTTP consumer mapped inbound wire headers of that form onto the Exchange, where an undertow WebSocket producer reads them as dispatch directives and can be made to deliver to a peer other than the one the route selected; and header names that undertow itself does not accept were mapped onto the Exchange ra

    Product
    Apache Camel
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026rConfig Core 8.0.0 before 8.2.10 contains an authentication bypass vulnerability that allows unauthenticated attackers to self-register accounts with full AdminCVE-2026-77915 · Other software · rconfig · reported by VulnCheckCritical 9.3

    rConfig Core 8.0.0 before 8.2.10 contains an authentication bypass vulnerability that allows unauthenticated attackers to self-register accounts with full Administrator privileges due to a duplicate bare Auth::routes() call in routes/web.php that re-enables the POST /register route after it was explicitly disabled. Attackers can register a new account that is immediately authenticated with Admin-level access because the registration controller does not assign a role and the users.role column defaults to Admin, enabling access to stored device credentials, user data, and API token issuance.

    Product
    rconfig
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026rConfig Core 8.0.0 before 8.2.13 contains a path traversal vulnerability that allows authenticated users to read arbitrary files by supplying crafted filenames CVE-2026-77914 · Other software · rconfig · reported by VulnCheckHigh 7.1

    rConfig Core 8.0.0 before 8.2.13 contains a path traversal vulnerability that allows authenticated users to read arbitrary files by supplying crafted filenames containing directory traversal sequences to the export download endpoint. Attackers can manipulate the filename parameter with traversal sequences to escape the intended export directory and access files outside it that are readable by the application process.

    Product
    rconfig
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Unauthenticated REST disclosure of certain content items in Apache Allura.CVE-2026-75099 · Websites & servers · Apache Software Foundation · reported by security@apache.orgMedium 5.3

    Unauthenticated REST disclosure of certain content items in Apache Allura. This issue affects Apache Allura: through 1.19.1. Users are recommended to upgrade to version 1.20.0, which fixes the issue.

    Product
    Apache Allura
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Improper input validation vulnerability in Apache Camel Atmosphere Websocket component.CVE-2026-71300 · Email & office · Apache Software Foundation · reported by security@apache.orgCritical 9.8

    Improper input validation vulnerability in Apache Camel Atmosphere Websocket component. This issue affects Apache Camel: from 4.0.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0. The camel-atmosphere-websocket producer selects which connected WebSocket peers a message is delivered to through Exchange headers, and the string values of those headers sat outside the Camel namespace: websocket.connectionKey and websocket.connectionKey.list, along with websocket.sendToAll, websocket.eventType and websocket.errorType. WebsocketEndpoint extends ServletEndpoint and so inherits HttpHeaderFilterStrategy, which filters only the Camel and camel prefixes; the dotted names therefore fell outside the filtered namespace and were admitted in both directions by every HTTP-family consumer. In a route bridging an HTTP consumer into an atmosphere-websocket producer, an external sender could supply the list header and take over the producer's dispatch decision. WebsocketProducer.process tests the list header before the single-key header, so an injected value discarded the recipient the route had selected: a notification intended for one connected client could be suppressed, o

    Product
    Apache Camel
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Improper Authentication vulnerability in Apache Camel Platform HTTP Main component.CVE-2026-66908 · Websites & servers · Apache Software Foundation · reported by security@apache.orgHigh 7.5

    Improper Authentication vulnerability in Apache Camel Platform HTTP Main component. This issue affects Apache Camel: from 4.8.0 before 4.22.0. The camel-main embedded HTTP server can protect its endpoints with JWT authentication, configured through authenticationEnabled together with the JWT keystore properties. JWTAuthenticationConfigurer.buildJwtOptions returned null when neither jwtIssuer nor jwtAudience was configured, and the caller then skipped the JWTAuthOptions.setJWTOptions call entirely, so the Vert.x JWTAuth instance was built from the keystore alone. The result was that inbound tokens were checked only for signature and expiry: the iss and aud claims were not validated at all. Nothing signalled this - the server started normally and reported no warning - so a deployment configured the documented way silently enforced less than the operator believed it had enabled, and the component documentation itself presented signature and expiry checking as the default with issuer and audience as an optional extra. Both the application server and the management server were affected, because the omission was in each of the two configureAuthentication paths. Any unexpired token

    Product
    Apache Camel
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Relative path traversal vulnerability in Apache Camel Google Storage component.CVE-2026-66907 · Email & office · Apache Software Foundation · reported by security@apache.orgHigh 7.5

    Relative path traversal vulnerability in Apache Camel Google Storage component. This issue affects Apache Camel: from 4.0.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0. The camel-google-storage consumer downloads Google Cloud Storage objects to the local filesystem when the downloadFileName option is set. That option is documented as a folder or a filename, and when its value contains no expression token the consumer builds the local destination by appending the object name to it: evaluateFileExpression sets the Exchange file-name header to the remote object name and evaluates downloadFileName + "/${file:name}". The ${file:name} token returns the file-name header verbatim, unlike ${file:onlyname}, which applies FileUtil.stripPath to it. The resulting string was passed directly to new File(result) and blob.downloadTo(file.toPath()) with no lexical normalization and no check that the destination stayed inside the configured directory. The object name is not route-controlled data: the consumer lists the bucket, iterates every returned blob and creates one exchange per object from blob.getBlobId().getName() verbatim, and the filter option that could restri

    Product
    Apache Camel
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Relative path traversal vulnerability in Apache Camel Azure Storage Blob component.CVE-2026-66906 · Email & office · Apache Software Foundation · reported by security@apache.orgCritical 9.1

    Relative path traversal vulnerability in Apache Camel Azure Storage Blob component. This issue affects Apache Camel: from 4.0.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0. The camel-azure-storage-blob component can download an Azure Storage blob to the local filesystem through its downloadBlobToFile operation, writing into the directory named by the fileDir endpoint option, which is documented as usable from both the producer and the consumer. BlobOperations.downloadBlobToFile built the local target by joining fileDir with the remote blob name exactly as the Azure SDK reported it (new File(fileDir, client.getBlobName())) and passed the result straight to the SDK download call, with no lexical normalization and no check that the resolved location stayed inside fileDir. The blob name is not route-controlled data: the consumer enumerates the container in BlobConsumer.createBatchExchangesFromContainer, which lists blobs and creates one exchange per entry from BlobItem.getName() verbatim, applying no name filtering by default. A blob name containing parent-directory segments therefore resolved to a location outside the configured fileDir, letting anyone ab

    Product
    Apache Camel
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Improper Input Validation, Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') vulnerability in Apache Camel KnatCVE-2026-63621 · Email & office · Apache Software Foundation · reported by security@apache.orgMedium 5.3

    Improper Input Validation, Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') vulnerability in Apache Camel Knative component The Knative consumer in camel-knative maps inbound CloudEvent attributes onto Camel message headers. In binary content mode the HTTP-header path filters Camel-internal headers through KnativeHttpHeaderFilterStrategy, but in structured content mode (Content-Type application/cloudevents+json) the CloudEvent extension fields are read directly from the JSON body and every extension key is copied into the Exchange headers without applying any HeaderFilterStrategy (CloudEventProcessors, spec versions 1.0, 1.0.1 and 1.0.2). As a result, an unauthenticated attacker can inject Camel-internal headers (e.g. CamelHttpUri, CamelHttpPath, CamelFileName) via a structured-mode CloudEvent request, matched case-insensitively against Camel's header map. When a route forwards messages from a Knative consumer to a header-driven component such as camel-http or camel-file, the injected headers override configured values, enabling server-side request forgery (SSRF), path traversal or message-dispatch redirection depending on the rout

    Product
    Apache Camel
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Relative path traversal vulnerability in Apache Camel Azure-Storage Datalake component This issue affects Apache Camel: from 4.0.0 before 4.14.9, from 4.15.0CVE-2026-60093 · Email & office · Apache Software Foundation · reported by security@apache.orgMedium 5.5

    Relative path traversal vulnerability in Apache Camel Azure-Storage Datalake component This issue affects Apache Camel: from 4.0.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0. The camel-azure-storage-datalake component can download an Azure Data Lake Storage Gen2 file to the local filesystem through its downloadToFile operation, writing into the directory named by the fileDir endpoint option. DataLakeFileOperations.downloadToFile built the local target by joining fileDir with the remote path name exactly as the Azure SDK reported it (new File(fileDir, fileClientWrapper.getFileName())) and passed the result straight to the SDK download call, with no lexical normalization and no check that the resolved location stayed inside fileDir. The remote name is not route-controlled data: the consumer enumerates the filesystem in DataLakeConsumer.createBatchExchangesFromPath, which lists paths and creates one exchange per entry from PathItem.getName() verbatim, applying no name filtering by default. A path name containing parent-directory segments therefore resolved to a location outside the configured fileDir, letting anyone able to influence the names present in

    Product
    Apache Camel
    What to do
    Apply the vendor’s update. The NVD record links to the advisory.
  • Aug 24, 2026Improper input validation vulnerability in Apache Camel.CVE-2026-59230 · Email & office · Apache Software Foundation · reported by security@apache.orgMedium 6.5

    Improper input validation vulnerability in Apache Camel. This issue affects Apache Camel: from 2.17.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0. The camel-mail component ships a MimeMultipart data format that can unmarshal a MIME multipart message. When it is configured with headersInline set to true, the unmarshal path copies the MIME headers of the incoming message onto the Camel message: it enumerates every header that is not one of the three standard ones it generates itself - Message-ID, MIME-Version and Content-Type - and calls setHeader for each, applying no HeaderFilterStrategy. The names of those MIME headers come from the message being unmarshalled, so a sender able to influence the message could place a header whose name falls in the Camel-internal namespace and have it set on the Exchange. Camel components read control headers from that namespace to override their configured behaviour - the camel-sql producer, for instance, takes the statement to execute from a Camel header when one is present - so an injected header could redirect what a downstream step in the route does with data the route author never intended it to take from the messa

    Product
    Apache Camel
    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.