ViWeb Security Briefings

Short, source-based guidance on website and hosting security issues that matter to business website owners.

Scope and update schedule

Curated website and hosting security guidance drawn from public advisories and vendor records within ViWeb's service scope. Entries are general guidance, not a diagnosis of any particular site, and they do not provide complete or real-time coverage.

ViWeb researches daily at 10:00 Vietnam time. Entries are published when a useful, verified change exists, so daily research does not mean daily publication. Each entry shows the absolute date it was last verified. Check the original advisories before acting.

Page 1 of 5

  1. Attention Exploitation not established

    Accept Stripe Payments through 2.1.4 allows stored XSS through comment links, fixed in 2.1.5

    Identifiers: CVE-2026-130323

    Accept Stripe Payments

    Accept Stripe Payments, the WordPress plugin with slug stripe-payments from Tips and Tricks HQ, is affected through version 2.1.4 inclusive under CVE-2026-130323. Wordfence Intelligence disclosed the issue on November 20, 2026. Links in comments submitted by unauthenticated users can cause script to run in a viewer's browser only when an affected page renders such a link and, in the usual path, the viewer clicks it. The fix is in 2.1.5. The developer changelog on wordpress.org confirms related changes to popup and prefetch link construction without naming the CVE. This concerns the WordPress plugin only and does not indicate any incident on Stripe's platform or any payment-card breach.

    Who is affected: Applies to sites running Accept Stripe Payments 2.1.4 or earlier where a comment link from an untrusted commenter is rendered on a page. With default settings, the disclosed path requires a viewer to click that link. The separate page-load path applies only when the non-default Prefetch Payment Popup Scripts option is enabled and such a link is present on the page. Enabling prefetch alone, without affected comment content, does not establish exposure.

    Last substantive change
    Last verified

    Last verified: . Attention items are due for re-verification within 72 hours.

  2. Attention Exploitation not established

    ElasticPress through 5.3.5 stores unauthenticated input shown to admins in Failed Queries, fixed in 5.3.6

    Identifiers: CVE-2026-116518 · GHSA-6hx4-m9fj-4m2q

    ElasticPress

    ElasticPress, the WordPress plugin with slug elasticpress from 10up, is affected through version 5.3.5 inclusive under CVE-2026-116518. Unauthenticated input can be stored by the affected logging path and later rendered when an administrator opens the plugin's Status Report and expands the Failed Queries section. 10up released 5.3.6 on November 11, 2026 and its release notes describe the matching fix. Wordfence Intelligence disclosed the issue on November 20, 2026 and the CVE record was published on November 21. Patchstack lists the same affected and fixed versions and refers to Wordfence.

    Who is affected: Applies to sites running ElasticPress 5.3.5 or earlier. Two steps are involved. Unsafe input is first stored in the plugin's failed-query log by the affected logging path. An administrator later opens the Status Report and expands the Failed Queries section, where the stored entry is rendered. A normal visitor viewing search results is not exposed by that step alone.

    Last substantive change
    Last verified

    Last verified: . Attention items are due for re-verification within 72 hours.

  3. Attention Exploitation not established

    GPGME double-free needs a consumer inventory and updates

    Identifiers: CVE-2026-129975

    GPGME

    GnuPG disclosed CVE-2026-129975 (T8557) on November 20, 2026, a double-free memory-handling bug in GPGME (GnuPG Made Easy). An application that uses the library can reach the bug when it processes malicious OpenPGP data. The upstream advisory covers GPGME versions before 2.3.0, and 2.3.0 was never publicly available, so the public mainline fix is GPGME 2.3.1. GnuPG's legacy maintainer has also released 1.24.4 as an explicit fix for the older line, while warning that future security patch coverage for that line is not guaranteed. Vendor backports can carry smaller package versions, for example Debian 13 (trixie) gpgme1.0 1.24.2-3+deb13u1 and Debian 12 (bookworm) 1.18.0-3+deb12u1, so judge each copy by its own package or update channel rather than by comparing it with the upstream number. The Gpg4win project advisory states that Gpg4win 5.1.2 includes the fix for Windows desktops. The reviewed sources do not establish real-world exploitation.

    Who is affected: You are affected only when both conditions hold: the system has a GPGME copy without the fix for its package or update channel, whether as a shared library, a dynamic Windows library, or a bundled or statically linked copy inside an application or container image, and a consumer passes untrusted OpenPGP material to that copy, such as inbound signed data. Not every mail client, PGP command-line tool, GitLab deployment, web server, or signature-verification task relies on GPGME. Which component and which data paths are involved is an inventory question, not an assumption.

    Last substantive change
    Last verified

    Last verified: . Attention items are due for re-verification within 72 hours.

  4. Attention Exploitation not established

    Node.js November 2026 security release fixes HTTP/2, HTTPS and TLS flaws

    Identifiers: CVE-2026-123863 · CVE-2026-123864 · CVE-2026-123865 · CVE-2026-123866 · CVE-2026-126051 · CVE-2026-123872 · CVE-2026-123874 · CVE-2026-123828 · CVE-2026-123867 · CVE-2026-123868 · CVE-2026-123871 · CVE-2026-123877 · CVE-2026-123875 · CVE-2026-123829 · CVE-2026-123862 · CVE-2026-106071

    Node.js 22.x, Node.js 24.x, Node.js 26.x

    On 11 November 2026 the Node.js project published a security release for the 22.x, 24.x and 26.x lines, with fixed versions 22.23.5, 24.22.3 and 26.13.1. The umbrella announcement describes sixteen issues, the highest rated High, concentrated in the HTTP/2 server, HTTPS request parsing, TLS handshake and client-certificate handling, the https.Agent session cache, proxy error messages, zlib streaming and the Permission Model. Each flaw has its own preconditions. This is not a single unauthenticated remote code execution that applies to every Node application.

    Who is affected: Lines listed per issue in the umbrella: CVE-2026-123863, CVE-2026-126051, CVE-2026-123874, CVE-2026-123828 and CVE-2026-123868 list 24.x and 26.x; CVE-2026-123864, CVE-2026-123865, CVE-2026-123866, CVE-2026-123872, CVE-2026-123867, CVE-2026-123871, CVE-2026-123877, CVE-2026-123875, CVE-2026-123829, CVE-2026-123862 and CVE-2026-106071 list 22.x, 24.x and 26.x. The 22.23.5 release notes also carry fixes for some items the umbrella lists for 24.x and 26.x only; take the fix without treating that as proof 22.x was exposed. Conditions matter: CVE-2026-123864 needs Node's own HTTPS server with a handler that flushes headers before the request body ends and later ends the response with a non-empty chunk, and reading the leaked memory also needs an ordinary route that echoes or stores a request body; cleartext node:http is not affected. HTTP/2 issues need an actual node:http2 server, and several are reachable over cleartext; CVE-2026-123874 and CVE-2026-123875 also need respondWithFile or respondWithFD, and CVE-2026-123828 needs attacker-controlled input passed to altsvc. CVE-2026-126051 needs SNI, OCSP or session hooks or addContext. CVE-2026-123872 and CVE-2026-123867 need per-hostname client-certificate policies. CVE-2026-123877 affects outbound https.Agent use with mixed CA options. CVE-2026-123871 needs a malformed proxy URL in the environment. CVE-2026-123862 needs zlib params during streaming. The Permission Model items apply only under --permission, and CVE-2026-123829 only on macOS and Windows. The upstream announcement treats end-of-life lines as always affected; they receive no fix in this upstream release.

    Last substantive change
    Last verified

    Last verified: . Attention items are due for re-verification within 72 hours.

  5. Attention Exploitation not established

    Linux KVM on AMD: CVE-2026-99312 conditional guest escape with nested virtualization

    Identifiers: CVE-2026-99312

    Linux KVM host with AMD nested virtualization

    The Linux kernel CNA announced CVE-2026-99312 on November 18, 2026, and DigitalOcean published its original disclosure on November 19, 2026. The issue is in KVM nested SVM on AMD hosts with nested virtualization enabled, and vendor analysis assumes the attacker can act as root inside a guest on such a host. The CNA record lists the affected stable branches and names 6.12.118, 6.18.64 and 7.3.5 as example versions that carry the fix upstream.

    Who is affected: Applies to KVM hosts on AMD processors with nested virtualization enabled. Distribution status is separate from the upstream record. As of November 21, 2026, the Ubuntu CVE tracker lists the Noble linux package and the Jammy linux-aws-6.8 package as Vulnerable, with no fixed revision on those rows; other Ubuntu kernel variants must be checked individually on the tracker rather than inferred. Ubuntu users should not install raw upstream kernels.

    Last substantive change
    Last verified

    Last verified: . Attention items are due for re-verification within 72 hours.

  6. Attention Exploitation not established

    Thim Kit for Elementor: stored script injection through post comments, fixed in 1.4.9

    Identifiers: CVE-2026-122230

    Thim Kit for Elementor

    Wordfence Intelligence published CVE-2026-122230 on November 20, 2026, credited to UKO. It affects the WordPress plugin Thim Kit for Elementor (slug thim-elementor-kit) in versions 1.4.8 and earlier; Patchstack lists the same range and cites Wordfence as its source. The plugin's WordPress.org release readme shows version 1.4.9 available since November 4, 2026, so the fix predates the public disclosure. The issue is in this plugin, not in Elementor itself.

    Who is affected: Applies when the plugin is at 1.4.8 or earlier and a Single Post template uses the plugin's Post Comment widget with the Text Reveal entrance animation in the initial viewport, with attacker-supplied comments visible to visitors. Exposure includes comments that moderation lets through, or sites where moderation is off. A normal page visit can render the unsafe content.

    Last substantive change
    Last verified

    Last verified: . Attention items are due for re-verification within 72 hours.

  7. Attention Exploitation not established

    Ubuntu nginx packages: USN-9182-1 fixes two issues on 24.04 LTS and three on 22.04 LTS

    Identifiers: USN-9182-1 · CVE-2026-125283 · CVE-2026-123640 · CVE-2026-118899

    Ubuntu Noble nginx packages, Ubuntu Jammy nginx packages

    Canonical published USN-9182-1 on November 20, 2026 for Ubuntu-provided nginx packages. It covers CVE-2026-125283, CVE-2026-123640 and CVE-2026-118899, with applicability listed per release. Canonical's per-CVE tracker pages show CVE-2026-125283 and CVE-2026-123640 fixed on Ubuntu 24.04 LTS (Noble) in 1.24.0-2ubuntu7.21, the supported update named in this notice, and all three CVEs fixed on 22.04 LTS (Jammy) in 1.18.0-6ubuntu14.24. CVE-2026-118899 had already been fixed on Noble in the earlier revision 1.24.0-2ubuntu7.20, so the 7.21 update also carries that fix.

    Who is affected: Only nginx packaged by Ubuntu for 24.04 LTS and 22.04 LTS. Copies installed from nginx.org, container images or hosting panels follow their own vendor or image and are not covered by this notice. Whether an earlier revision is affected depends on the installed package and configuration; earlier revisions should not all be assumed vulnerable without package evidence. The nginx.org change index corroborates the upstream fixes, but its version numbers are not comparable with Ubuntu package labels.

    Last substantive change
    Last verified

    Last verified: . Attention items are due for re-verification within 72 hours.

  8. Attention Exploitation not established

    WP Fastest Cache <=1.5.4: directory deletion outside the cache area (CVE-2026-119114)

    Identifiers: CVE-2026-119114

    WP Fastest Cache

    Wordfence Intelligence published and updated a notice for CVE-2026-119114 on November 20, 2026, credited to Jakub Herman. It affects the WordPress directory plugin WP Fastest Cache (slug wp-fastest-cache) up to and including version 1.5.4 and is fixed in 1.5.5. The report describes deletion of directories and files outside the intended WordPress cache area, which can break a website. Wordfence states that the described path requires Custom Permalinks or GeoDirectory to be installed alongside WP Fastest Cache and does not require the attacker to be logged in. The plugin changelog confirms that 1.5.5 adds path validation before cache deletion and also changes purge behaviour and header-based caching rules, so owners should recheck their cache exclusions, meaning the pages they have told the plugin never to cache, after updating.

    Who is affected: Sites running WP Fastest Cache 1.5.4 or earlier from the WordPress directory. The reported path applies when Custom Permalinks or GeoDirectory is installed alongside it. A site still needs the 1.5.5 update even if it cannot establish that combination. This is a separate issue from CVE-2026-111464, which was fixed in 1.5.4.

    Last substantive change
    Last verified

    Last verified: . Attention items are due for re-verification within 72 hours.

  9. Attention Exploitation reported

    Drupal core installer flaw CVE-2026-132165 reported exploited: update to 10.6.22, 11.3.22 or 11.4.13 or later

    Identifiers: CVE-2026-132165 · CVE-2026-132166 · SA-CORE-2026-017 · SA-CORE-2026-018

    Drupal core installer (CVE-2026-132165), Drupal core deserialization chain (CVE-2026-132166)

    On 18 November 2026 the Drupal Security Team published two core advisories. SA-CORE-2026-017 (CVE-2026-132165) concerns conditions under which the installer path of an already installed site can be reached. On 20 November 2026 the team updated that advisory, raising it from Critical, 18/25, to Highly critical, 20/25, with an exploitation rating of E:Exploit, and stating it had received a report that the flaw was exploited on live sites as early as 19 November 2026 at 19:00 UTC. SA-CORE-2026-018 (CVE-2026-132166) is unchanged: it is rated 14/25, is not Critical, and concerns a conditional deserialization chain that only becomes exploitable when combined with a separate unsafe deserialization flaw. Both are fixed in Drupal 10.6.22, 11.3.22 and 11.4.13.

    Who is affected: Affected: Drupal core <10.6.22, >=11.0.0 <11.3.22, and >=11.4.0 <11.4.13. Fixed: 10.6.22, 11.3.22 and 11.4.13. These are version floors: any later supported release in the same branch also contains the fix, and a site already on a later patched release should not be moved back to the exact floor. Drupal 10.5.x and older within the 10 series, 11.2.x and older within the 11 series, and Drupal 8 and 9 no longer receive security coverage and get no fix; those sites must move to a supported line. Drupal Steward protection for the known vectors of SA-CORE-2026-017 applies only to its subscribers and, according to the vendor, does not remove the need to update. The 20 November release notes for the three fixed versions describe a separate theme registry regression that affects some custom and contributed code, including Search API. The notes say Drupal 11.4.14 is planned to address that regression; it is not the security fix, and its availability is not verified here. The release notes suggest affected 11.3.22 and 10.6.22 sites consider moving to the 11.4 line to receive that regression fix once it is available. Distribution and hosting panel packages need their own confirmation.

    Last substantive change
    Last verified

    Last verified: . Attention items are due for re-verification within 72 hours.

  10. Attention Exploitation not established

    PHP security releases 8.2.36, 8.3.37, 8.4.28 and 8.5.13 published on 19 November 2026

    Identifiers: PHP-November-2026-security-advance · CVE-2026-126714 · CVE-2026-115560 · CVE-2026-129289

    PHP file session handler (CVE-2026-126714), PHP session serialization (CVE-2026-115560), PHP-FPM (CVE-2026-129289)

    On 19 November 2026 the PHP project published security releases 8.2.36, 8.3.37, 8.4.28 and 8.5.13 for its supported branches, one day after its advance notice of 18 November. Three advisories reviewed for this briefing cover two session handling flaws, CVE-2026-126714 and CVE-2026-115560, and one PHP-FPM issue, CVE-2026-129289. Each depends on conditions beyond running an affected version. PHP 8.6.0, released the same day, is a new branch and is not required to patch an existing supported branch. On 21 November 2026 we corrected the Ubuntu packaging status: the Ubuntu security tracker lists fixed php8.3 and php8.1 package versions for CVE-2026-126714 and CVE-2026-129289, while CVE-2026-115560 remains under evaluation for those packages. For deployments that run a vulnerable PHP build behind Cloudflare, its managed rules for two of the three issues are a supplementary layer during and after the update, not a replacement for it. This briefing covers a selection of relevant issues and is not an exhaustive count. The information here was last verified on 21 November 2026.

    Who is affected: Websites running upstream PHP 8.2.x below 8.2.36, 8.3.x below 8.3.37, 8.4.x below 8.4.28 or 8.5.x below 8.5.13. Distribution and vendor packages carry their own version labels, so upstream version numbers do not describe their patch state. When read directly on 21 November 2026, the Ubuntu security tracker listed CVE-2026-126714 and CVE-2026-129289 as fixed in php8.3 8.3.6-0ubuntu0.24.04.14 for Ubuntu 24.04 Noble and in php8.1 8.1.2-1ubuntu2.29 for Ubuntu 22.04 Jammy, with CVE-2026-115560 still needing evaluation for both packages. Those entries say nothing about other November advisories, and they do not show whether a given server has installed the fixed package version and restarted its PHP services. The status of other distributions and vendors must be confirmed with each of them. Older unsupported upstream branches are not covered and need a supported upgrade plan or evidence of a specific vendor backport. Separately packaged control panel PHP, worker runtimes and container images must each be checked on their own. A deployment that runs a vulnerable PHP build behind Cloudflare remains in scope, because the managed rules inspect only traffic routed through Cloudflare and do not change the PHP build.

    Last substantive change
    Last verified

    Last verified: . Attention items are due for re-verification within 72 hours.

  11. Attention Exploitation not established

    Certbot 5.10.0 fixes a local webroot authenticator flaw (GHSA-9qv6-9g6h-3x7x); no CVE assigned yet

    Identifiers: GHSA-9qv6-9g6h-3x7x

    Certbot webroot authenticator

    The Certbot project released 5.10.0 on 10 November 2026 with the fix, and published advisory GHSA-9qv6-9g6h-3x7x on 20 November 2026 (updated the same day). No CVE is assigned in the vendor notice at the time of checking. The vendor describes a local vulnerability in the webroot authenticator: a lower-privileged local account that can write to the webroot, or to a relevant parent directory or path component, may cause unauthorized ownership or permission changes while a higher-privileged Certbot creates challenge directories. The advisory scenario is Certbot run as root. Upstream Certbot before 5.10.0 is affected; 5.10.0 and later are fixed.

    Who is affected: Upstream Certbot <5.10.0 is affected and >=5.10.0 is fixed. It matters where the webroot authenticator is used, Certbot runs with higher privileges than some local accounts, and one of those accounts can write to the webroot or a relevant parent directory or path component. Shared hosting, where one privileged renewal job serves many customer directories, is one example of such a layout; single-tenant servers with separate deploy or application accounts can also qualify. Distribution packages, containers and hosting panels that bundle Certbot deliver fixes on their own schedule and may backport under older version numbers, so their own advisory or changelog is the evidence that counts.

    Last substantive change
    Last verified

    Last verified: . Attention items are due for re-verification within 72 hours.

  12. Attention Exploitation not established

    NextGEN Gallery plugin: three stored cross-site scripting issues disclosed, update to 4.5.6 or later

    Identifiers: CVE-2026-119611 · CVE-2026-109387 · CVE-2026-116550

    NextGEN Gallery (CVE-2026-119611), NextGEN Gallery (CVE-2026-109387), NextGEN Gallery (CVE-2026-116550)

    On 19 November 2026 Defiant, the company behind Wordfence, published three vulnerability records in Wordfence Intelligence for the WordPress plugin NextGEN Gallery, listed in the plugin directory as Photo Gallery, Sliders, Proofing and Themes, with the slug nextgen-gallery. All three are stored cross-site scripting issues. Each record lists versions up to and including 4.5.5 as affected and 4.5.6 as patched. The plugin's official readme on the WordPress plugin repository independently records 4.5.6 in its changelog under its own dated entry, with escaping and security changes, and showed a stable tag of 4.6.0 when retrieved. The 19 November date is the disclosure date. The fix was already recorded in that earlier changelog entry. The three identifiers are CVE-2026-119611, which involves a gallery tag AJAX pagination and cache path, CVE-2026-109387, which requires a user permitted to edit images to import a file supplied by an untrusted party, and CVE-2026-116550, which requires a public comment to reach rendered content while a broader, non-default lightbox setting is in use.

    Who is affected: Applies to WordPress sites running NextGEN Gallery version 4.5.5 or earlier. Check the exact slug nextgen-gallery, since several gallery plugins have similar names. Sites already on 4.5.6 or later, including the 4.6.0 stable tag seen on the readme, are listed as patched for these three issues. Sites that accept public comments on gallery content, import images from outside sources, or use non-default lightbox settings meet more of the described conditions. Sites that do not use the plugin are not affected by these records.

    Last substantive change
    Last verified

    Last verified: . Attention items are due for re-verification within 72 hours.