The Exploit Bulletin — Thursday, November 12, 2026: 4 issues require action
Thursday, November 12, 2026 — 4 issues require action. If you run none of the software below, you are done.
Affects: Craft CMS · Drupal core · openDCIM · Xen Orchestra
1. Unauthenticated SQL injection in Craft CMS element search grants administrator access (CVE-2026-123488)
PRIVILEGE ESCALATION · CRITICAL · CVSS 9.3
VulnCheck added this flaw to its known-exploited catalog on 2026-11-11 and three public exploits are available, so any site that uses craft.search on a MySQL/MariaDB backend and has not updated to 4.18.9 or 5.11.2 can have an administrator account created with a single unauthenticated request.
The front-end element search endpoint in Craft CMS concatenates the attribute parameter into a SQL query unsanitized, and because PDO runs with emulated prepares, stacked statements execute on MySQL/MariaDB backends. An unauthenticated attacker gets read and write access to the database and can set the admin flag or overwrite password hashes in the users table to become an administrator.
Affected: Craft CMS >= 4.0.0 < 4.18.9; Craft CMS >= 5.0.0 < 5.11.2; Only sites on MySQL/MariaDB whose front-end templates use craft.search
How to Test: Check the Craft CMS version in the Control Panel or in composer.lock: 4.x below 4.18.9 and 5.x below 5.11.2 are affected if the database is MySQL or MariaDB and any front-end template performs a search via craft.search. Review web server logs for front-end requests containing [attribute] or %5Battribute%5D in the query string, which is the injection point. In the users table, check whether the admin flag has been set on user ID 1 or any other account and whether password hashes changed unexpectedly; review the Control Panel for new or elevated administrator accounts.
How to Patch: Update to Craft CMS 4.18.9 or 5.11.2. If you cannot update immediately, block front-end requests containing %5Battribute%5D or [attribute] anywhere in the query string as a temporary mitigation.
Evidence: VulnCheck KEV · VulnCheck XDB public exploit · VulnCheck XDB public exploit · VulnCheck XDB public exploit
2. Unsafe reflection in Field UI gives remote code execution on Drupal core (CVE-2026-108097)
REMOTE CODE EXECUTION · CRITICAL · CVSS 8.1
VulnCheck added this flaw to its known-exploited catalog on 2026-11-11 after its canary sensors recorded exploitation attempts, and public exploit code exists, so an unpatched Drupal site with a vulnerable contributed module can be taken over without credentials.
The Field UI module in Drupal core accepts externally controlled input to select classes (unsafe reflection), leading to remote code execution. Core alone is not directly exploitable, but multiple exploit paths exist through contributed modules and at least one known path requires no authentication; custom code can also expose the vulnerable functionality.
Affected: Drupal core >= 8.9.0 < 10.6.19; Drupal core >= 11.0.0 < 11.3.19; Drupal core >= 11.4.0 < 11.4.10; Drupal core >= 12.0.0-alpha1 < 12.0.0-beta2; Drupal 8, 9, 10.5.x and earlier, 11.2.x and earlier: end-of-life, no fix
How to Test: Check the Drupal core version shown in the admin Status report or in your composer.lock: anything below 10.6.19 (10.x), 11.3.19 (11.3.x), 11.4.10 (11.4.x) or 12.0.0-beta2 is affected, and any site still on Drupal 8, 9, 10.5.x or 11.2.x is end-of-life and vulnerable. Confirm whether the core Field UI module (field_ui) is enabled and which contributed modules expose it. Review web server and watchdog logs for unexpected requests to Field UI routes, newly created or modified PHP files, unexpected admin accounts and changes to the files directory; sites behind Drupal Steward are protected from some but not all known attack vectors.
How to Mitigate: Update Drupal 11.4.x to 11.4.10, Drupal 11.3.x to 11.3.19, and Drupal 10.6.x to 10.6.19. Drupal 11.2.x and below and 10.5.x and below are end-of-life, as are Drupal 8 and 9; migrate to a supported release. Until the update is applied, uninstall the core Field UI module (field_ui), which the Drupal Security Team states provides protection.
Evidence: VulnCheck KEV · VulnCheck XDB public exploit · VulnCheck XDB public exploit
3. Unauthenticated SQL injection in openDCIM install handlers chains to remote code execution, no upstream fix merged (CVE-2026-28516)
REMOTE CODE EXECUTION · CRITICAL · CVSS 9.3
VulnCheck added the flaw to its known-exploited catalog on 2026-11-12 after its canary sensors recorded exploitation attempts the same day, a public exploit is available, and the maintainer closed the fix pull request unmerged, so unpatched instances must be hand-patched or isolated now.
openDCIM's install.php and container-install.php pass user input straight into SQL via Config::UpdateParameter without prepared statements. Combined with the exposed LDAP configuration form (CVE-2026-28515) and the dot command injection in report_network_map.php (CVE-2026-28517), the researcher's write-up chains this into remote code execution without credentials on Docker deployments and with authentication on Apache deployments.
Affected: openDCIM <= 23.04 (through commit 4467e9c4)
How to Test: You are affected if you run openDCIM 23.04 or any build at or before commit 4467e9c4 and config.inc.php's Config::UpdateParameter still builds SQL by string interpolation (the fixed form uses PDO named parameters). Docker/container deployments are exposed without credentials through container-install.php. Review web-server access logs for POST requests to install.php and container-install.php from unexpected sources, inspect the Config parameters table for unexpected values (particularly the dot path used by report_network_map.php), and check for unexpected processes or files on the host, since the chain ends in command execution.
How to Mitigate: No fixed openDCIM release exists — the upstream pull request #1664 (commit 8f7ab2a) was closed without merge. Apply its changes manually: replace the string-interpolated query in Config::UpdateParameter in config.inc.php with prepared statements; add a $person->SiteAdmin check before the LDAP form processing in install.php and container-install.php; and in report_network_map.php validate the dot command with is_executable() and wrap all exec() arguments in escapeshellarg(). Until patched, remove or block access to install.php and container-install.php on deployed instances and restrict the web interface to trusted networks.
Evidence: VulnCheck KEV · VulnCheck XDB exploit · Public exploit repository
4. Unauthenticated REST token bypass grants admin and enables root takeover of XCP-ng hosts; vendor reports exploitation (Xen Orchestra)
UNVERIFIED PUBLIC REPORT · NO CVE · AUTHENTICATION BYPASS · CRITICAL
Vates published the advisory and SecurityWeek reported it on 2026-11-11; the vendor says exploitation is already occurring, the bypass needs no credentials, and a patch is available, so XO operators should upgrade today.
Vates says a flaw in Xen Orchestra's REST authentication turns a supplied token into an empty object {} that is used as an unfiltered lookup, returning the first token in the collection; if that token is unexpired, the caller is authenticated as its owner. An unauthenticated attacker on the network can thus obtain administrator access to the XO control plane, and Vates states XO compromise can lead to arbitrary code execution on managed pools and full root takeover of XCP-ng nodes. SecurityWeek reports that Vates says a threat actor has been exploiting this bug together with a second, still-unfixed flaw that requires admin privileges and abuses VM imports to compromise XCP-ng hosts. Fixed releases are 6.9.2 (stable) and 6.10.1 (latest); Xen Orchestra Appliance is affected. Not known: no CVE has been assigned to either flaw, the earliest affected release is not stated, and the admin-level VM-import zero-day has no fix yet. Vates notes unauthorized access is not logged and that its IoCs cover only the observed campaign.
Affected: Xen Orchestra before 6.9.2 (stable) and before 6.10.1 (latest), including Xen Orchestra Appliance
How to Test: Check the version in the XO web UI (Settings > About / XOA update view) or xo-server --version; anything below 6.9.2 (stable) or 6.10.1 (latest), including unpatched XOA, is affected. Review proxy/web-server logs in front of XO for REST requests from 91.211.251.112 or Tor exit nodes, and audit for unexpected user tokens, unknown VM imports, new SSH keys or processes on XCP-ng hosts; Vates warns absence of these indicators does not rule out compromise because unauthorized access is not logged.
How to Patch: Update XOA via the built-in updater or rebuild XO from source to 6.9.2 (stable) or 6.10.1 (latest). If you cannot update now, firewall the XO HTTP/HTTPS interface to management networks or VPN only. After updating, revoke all existing authentication tokens, reset admin passwords, and review hosts for the VM-import follow-on attack, which remains unpatched.
Evidence: SecurityWeek: Critical Xen Orchestra Flaws Exploited in Attacks
Read on the web · Every past edition
The Exploit Bulletin is free and daily. It publishes only what security teams must act on today — nothing else. Forward it freely.
Spot an error, or an exploit we missed? Reply here or email [email protected].