Unauthenticated arbitrary file upload in the WordPress plugin Ultra Addons for Contact Form 7 (themefic) affects every version up to and including 3.5.50, allowing a remote attacker to place arbitrary files - including executable PHP - on the web server because the 'uacf7_wpcf7_mail_components' handler performs insufficient file-type validation. Successful exploitation requires the plugin's PDF Generator module to be explicitly enabled; that module is off by default, so default installations are not vulnerable, and RCE further depends on the uploaded file landing in a web-executable path. Vendor/NVD rates this 9.8 (AV:N/AC:L/PR:N/UI:N), while our assessment raises complexity to AC:H precisely because of that non-default module prerequisite; no public exploit code or confirmed active exploitation has been identified at time of analysis.
Unauthenticated arbitrary file upload in Addify's Request a Quote for WooCommerce plugin, affecting all versions up to and including 2.9.2, lets a remote attacker write executable files such as PHP into a web-accessible temporary RFQ upload directory by posting a file through the afrfq_submit_quote_via_popup() handler, which passes the attacker-supplied filename straight into move_uploaded_file() without extension or MIME validation. Exploitation depends on a non-default configuration: a public (unauthenticated-reachable) quote rule must exist and the multi-page popup quote flow must be enabled, which is what exposes the vulnerable handler; when those conditions are met no credentials or user interaction are required, consistent with the assessed vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (9.8). No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV), but given the low attack complexity and PHP code-execution outcome, any site running the popup RFQ flow should be treated as high priority.
Authenticated path traversal in Laranode before 1.2.1 lets any tenant holding a valid account and file manager access write arbitrary files outside their own home directory via the POST /filemanager/upload-file endpoint, including dropping PHP files into other tenants' web roots for code execution as those tenants. The endpoint built its destination as '/home/' + systemUsername + '/' + user-supplied path with no normalization or containment, so a low-complexity traversal request is sufficient on multi-tenant hosts where the web server interprets the written PHP; vendor CVSS 4.0 rates this 8.7 (AV:N/AC:L/AT:N/PR:L/UI:N) and our independent CVSS 3.1 assessment (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) equally reflects cross-tenant scope change. No public exploit code has been identified at time of analysis and the issue is not confirmed actively exploited (no CISA KEV entry); exploitation requires authentication, so single-tenant installations limit the blast radius to the attacker's own account.
Cross-site request forgery in the MCP Server for WordPress plugin (all versions before 1.8.2) allows unauthenticated attackers to perform administrator-only actions - including creating a brand-new administrator account - by tricking a logged-in WordPress administrator into visiting a crafted page. The plugin fails to correctly verify the WordPress REST API nonce for cookie-authenticated requests when an attacker-influenceable condition is present, so the victim's admin session is abused without any credential from the attacker (CVSS 3.1: 8.8, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, CWE-352). Publicly available exploit code exists per WPScan, but there is no confirmation of active exploitation (not in CISA KEV; SSVC exploitation: none) and EPSS is a low 0.10% (1st percentile); the practical gate is that a logged-in administrator must be lured to an attacker-controlled page while the vulnerable plugin is active.
Directory-context bypass in OpenClaw before 2026.8.1 allows authenticated attackers with user interaction to reuse an 'allow-always' exec approval to execute the same command against unreviewed files or repositories, escaping the original approved working directory. Exploitation requires a pre-existing 'allow-always' approval and the ability to influence agent behavior; it is not exploitable on a default installation with no standing approvals. No public exploit identified at time of analysis.
Stored cross-site scripting in the WP Review Slider Pro WordPress plugin (versions before 12.7.12) allows any authenticated user, including a Subscriber, to overwrite a live review submission form with unescaped field values because the AJAX save handler performs no capability check and issues a nonce to every visitor. A victim who later views the compromised public form has the injected script executed in their browser (user interaction required), yielding low confidentiality and integrity impact as assessed by CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N. Publicly available exploit code exists per WPScan, CISA's SSVC assessment records no observed exploitation, EPSS is only 0.16% (4th percentile), and a vendor patch is available in version 12.7.12.
Stored cross-site scripting in the WordPress plugin WP Review Slider Pro (wp-review-slider-pro) before 12.7.12 allows any authenticated user - including a low-privileged Subscriber - to persist arbitrary markup into review content that is later rendered without output escaping on public pages, executing script in the browser of any visitor who views them. The root cause is a missing capability check on an AJAX handler combined with a nonce that is issued to every visitor and therefore provides no authorization boundary; the published CVSS vector is network-reachable with low privileges and requires user interaction (CVSS:3.1/AV:N/AC:L/PR:L/UI:R), and although the reporting source scored it 8.0, an independent assessment scores it considerably lower (S:C/C:L/I:L/A:N) because impact is confined to the victim's browser session within the site origin. Publicly available exploit code exists, but there is no confirmed active exploitation (CISA SSVC exploitation: none) and EPSS is low at 0.16% (4th percentile); a vendor patch is available in version 12.7.12.
Cross-site scripting in the WordPress File Manager plugin (below 8.0.5), FileOrganizer (below 1.2.1) and File Manager Pro (below 2.1.3) allows an unauthenticated attacker to run arbitrary JavaScript inside the session of a logged-in administrator, because the file browser these plugins embed accepts window.postMessage events from any origin that is merely a leading-string prefix of the victim site's own address. Exploitation requires the administrator to be logged in and to visit an attacker-controlled page on such a prefix origin (for example a domain whose name begins with the victim's hostname), which is reflected in the CVSS vector as UI:R with AC:H while PR:N confirms no attacker authentication is needed. Publicly available exploit code exists and the vendor has released fixes, but CISA SSVC rates exploitation as none and automatable as no, and EPSS is only 0.17% (6th percentile), so this is a conditional rather than a mass-exploitation risk.
Unauthenticated attackers can create or overwrite arbitrary WordPress posts through the Testimonials Widget plugin's front-end testimonial submission form in versions up to 4.0.4. The missing capability and ownership check (CWE-862) lets any anonymous visitor change post titles, content, and authors without authentication or user interaction, with impact limited to content integrity. Publicly available exploit code exists, but EPSS is low at 0.14% (3rd percentile), SSVC reports no observed exploitation, and CISA KEV does not list the issue.
Stored cross-site scripting in the WP Directory Kit WordPress plugin before version 1.5.8 lets an authenticated user who holds the plugin's listing-management role (and who does not have the WordPress unfiltered_html capability) inject script into a listing's category and location fields, which the plugin then prints unescaped inside page attributes; the payload persists and executes for any anonymous visitor who views the affected directory page, requiring no further interaction from the victim. The attacker must already possess that elevated listing-management role and the plugin must be installed with directory listings in active use, so this is a genuine but conditional issue rather than a public-facing injection path. Publicly available exploit code exists, but there is no confirmed active exploitation (no CISA KEV listing) and EPSS is low at 0.15% (4th percentile); the vendor has released a fix in 1.5.8.
Unauthenticated SQL injection in the Bluff Post WordPress plugin (versions through 1.1.1) lets remote attackers inject into a SQL query and read sensitive data from the underlying WordPress database. The assessed vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N) confirms no authentication or user interaction is needed, but the attacker-supplied parameter is placed in a SQL identifier position rather than a quoted value, so exploitation requires blind/inference-based extraction and is consequently slower and more complex (AC:H); impact is confidentiality-only, with no integrity or availability effect assessed. Publicly available exploit code exists (WPScan references the issue as an exploit), but there is no CISA KEV entry and exploitation is not confirmed as active; EPSS is low at 0.17% (6th percentile), and SSVC records Exploitation: none, Automatable: no, Technical Impact: partial.
Stored cross-site scripting in the Optimole WordPress plugin (versions 4.0.0 through 4.2.12) allows an authenticated user with the WordPress Author role or higher to inject an event-handler attribute into the wrapper element of the plugin's video-player block; because that unrecognized attribute is rendered without escaping, the payload executes in the browser of any higher-privileged user - such as an administrator - who views the crafted post. Publicly available exploit code exists, and the vendor has released Optimole 4.2.13 to fix it. Risk is bounded: EPSS is only 0.15% (4th percentile), there is no CISA KEV listing, and CISA's SSVC assessment records no observed exploitation and no automatable vector, so this is a genuine but contained stored-XSS issue rather than a top-tier emergency.
WP Delicious versions before 1.10.8 are affected by a stored cross-site scripting flaw that lets Contributor-level and higher accounts inject arbitrary HTML, including script tags, through unescaped HTML tag names in recipe block data, with execution occurring when a victim views the recipe page. Publicly available exploit code exists, the vendor has released a patch in version 1.10.8, and EPSS is low at 0.15% (4th percentile); no KEV listing or active exploitation has been confirmed.
SQL injection in the WordPress plugin WP Review Slider Pro (wp-review-slider-pro) before 12.7.12 allows any authenticated user - including a low-privileged Subscriber - to inject arbitrary SQL into a plugin AJAX handler and read data from the site's database; because the queried results are then rendered to unauthenticated visitors, the extracted data can be exposed publicly rather than being confined to the attacker's own session. Exploitation requires a valid account on the target site (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, 6.5), which is trivial on sites that permit self-registration but blocked where registration is closed, and publicly available exploit code exists (no CISA KEV entry and no confirmed active exploitation; EPSS 0.16%, 5th percentile). Impact is confidentiality-only - no integrity or availability effect - but the leak-to-anonymous-visitors behavior makes this a genuine moderate-priority issue rather than a purely theoretical one.
Unauthenticated remote code installation in the lomart.fr 'UP' plugin for Joomla (versions 5.0.0-5.2.0 and 6.0.0-6.0.29) allows remote attackers to write and install arbitrary code on affected sites without authentication, user interaction, or non-default configuration, as reflected in the vendor's CVSS 4.0 base score of 10.0. The flaw is a path traversal (CWE-22) that lets attacker-supplied paths escape the intended directory and place executable content where the web server will run it, giving full compromise of confidentiality, integrity, and availability on the host and follow-on systems. This is a niche, single-vendor Joomla add-on, so exposure depends entirely on whether the plugin is installed and active; no public exploit has been identified at time of analysis and the issue is not confirmed as actively exploited (no CISA KEV listing).
Authentication bypass in the miniOrange OTP Login, Verification and SMS Notifications WordPress plugin (all versions up to and including 5.5.5) allows an unauthenticated remote attacker to log in as any existing administrator account by submitting only a known admin username, an empty password, and the POST parameter mo_wp_login_intent=otp - no password or OTP check is ever performed. Exploitation requires a specific, non-default configuration in which the site administrator has simultaneously enabled WP Login OTP, Login with Only OTP, Allow Users to Login with Username and Password, and Admin OTP Bypass; that prerequisite stack is the primary limiting factor and is why our independent assessment rates the issue AC:H rather than the AC:L assumed by the published 9.8 score, while the impact ceiling (full WordPress site takeover via an administrator session) remains high. No public exploit code has been identified and the vulnerability is not listed in CISA KEV, so risk is real but contingent on the vulnerable option combination being present; the upstream plugin repository shows a code fix commit.
Unauthenticated information disclosure in the File Manager WordPress plugin (versions 7.2.2 through before 8.0.5) lets remote attackers download database backup archives that the plugin leaves reachable in its directory, leaking every user's email address and password hash. The flaw only lands on servers that do not honor the plugin directory's .htaccess protection - nginx hosts or Apache with AllowOverride disabled - and it also depends on a backup archive having been generated and being reachable at a predictable or fixed filename, which is why the vendor and the independent assessment both score it AC:H and confidentiality-only (CWE-200, CVSS 5.9). Publicly available exploit code exists per WPScan, but there is no confirmed active exploitation (CISA SSVC: Exploitation none) and EPSS is low at 0.14% (3rd percentile), so exposure is best modeled as a realistic targeted/lateral-movement risk on non-compliant web server configurations rather than a mass-exploitation event.
Server-side request forgery (SSRF) in the Testimonials Widget WordPress plugin through version 4.0.4 allows unauthenticated remote attackers to make the server fetch arbitrary URLs and store the responses as publicly accessible files. This enables reading responses from internal services reachable from the WordPress server, though the impact is confidentiality-only and practical value depends on internal network reachability. Publicly available exploit code exists, and the EPSS score is 0.14% (3rd percentile), indicating a low predicted likelihood of exploitation.
Authenticated PHP code injection in the lomart.fr UP Plugin for Joomla (versions 5.0.0-5.2.0 and 6.0.0-6.0.29) allows a high-privilege administrator to execute arbitrary PHP code and system commands on the underlying server. The flaw requires a valid Joomla administrator account (PR:H) and is remotely exploitable without user interaction, but no public exploit code or active exploitation has been identified at time of analysis. Because the plugin is a narrowly deployed third-party extension and no vendor patch is available, the real-world priority is low despite the critical CVSS score (9.4), with mitigation limited to removing the plugin or tightly restricting administrative access.
Unauthenticated remote code execution in AcyMailing Enterprise for Joomla (versions before 11.1.0) lets anyone who can email the address monitored by the extension's 'mailbox action' feature write a PHP file into the site's web root, because inbound MIME parts are stored under media/com_acym/upload/ with no extension check (CWE-434); once reachable over HTTP and PHP-executable, that file runs as the web-server account. The gating precondition is that mailbox monitoring is enabled and the upload path is web-exposed, which is not a default configuration, but where it applies exploitation is trivial and requires no authentication (CVSS 4.0 9.5 with AT:P; independent assessment CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H, with the scope change reflecting impact escaping the extension into the hosting Joomla site). No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis; the vendor-released fix is AcyMailing Enterprise 11.1.0.
SQL injection in CloudClassroom-PHP-Project allows remote, unauthenticated attackers to manipulate the myfid parameter in mydetailsfaculty.php, resulting in limited confidentiality, integrity, and availability impact. Publicly available exploit code exists, but there is no confirmed active exploitation and no vendor-released patch because the project is unversioned and the maintainer did not respond. This is a genuine but low-priority issue that requires manual source-code remediation.
SQL injection in the 'eno' parameter handled by updatedetailsfromstudent.php in mathurvishal's CloudClassroom-PHP-Project lets remote attackers inject arbitrary SQL into the application's database queries, with limited confidentiality, integrity, and availability impact (CVSS 4.0 base 6.9; our independent assessment scores it 6.1 under CVSS 3.1). The project uses rolling releases with no version tags, so no fixed build or specific affected release can be pinned, and the maintainer was contacted but did not respond, leaving no vendor patch. Publicly available exploit code exists, including a GitHub advisory with a proof-of-concept; there is no confirmation of active exploitation (not in CISA KEV). This is a genuine but low-priority issue confined to a niche, non-commercial PHP application.
Privilege escalation in Kyverno before 1.19.1 allows an authenticated Kubernetes namespace tenant with Policy/apiCall authoring rights to escape namespace isolation and create objects as Kyverno's admission-controller ServiceAccount. The attacker supplies percent-encoded directory-traversal sequences in the Policy apiCall urlPath to bypass the per-namespace clamp, enabling creation of cluster-wide MutatingWebhookConfiguration objects or PolicyException objects in the kyverno namespace, with a path to cluster-admin escalation. No public exploit identified at time of analysis; vendor patch available in 1.19.1.
Privilege escalation in the Froxlor server administration panel (2.3.10 and earlier, including any build carrying only the earlier incomplete GHSA fix) lets an authenticated customer account with the data-export/DataDump feature enabled take ownership of arbitrary host directories, including /etc and other tenants' trees. The root-owned export cron runs `chown -R` through a symlink the customer plants at an intermediate path component of their export destination, because Froxlor\FileDir::makeCorrectDir() has an off-by-one in its path-component walk that skips the first segment below the customer home directory and ExportCron.php only validates the final component with is_link(). Exploitation is deterministic and needs no race, resulting in host root and cross-tenant compromise; the flaw is fixed in Froxlor 2.3.12, and no public exploit was identified at time of analysis.
Argument injection in the Froxlor hosting control panel (versions before 2.3.12) allows an authenticated administrator - or any actor able to write settings, such as through the settings-import API - to inject arbitrary acme.sh command-line options via the unescaped system.letsencryptchallengepath setting, resulting in arbitrary command execution as root the next time the Let's Encrypt cron job runs. The vendor CVSS 4.0 score of 9.4 (and the independently assessed CVSS 3.1 vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H) reflects complete compromise of the host, but exploitation is gated behind a high-privilege settings-write primitive (PR:H) and requires that acme.sh-based Let's Encrypt certificate issuance be configured so the root cron actually executes the poisoned command line. No public exploit code was identified at time of analysis and the issue is not reported as confirmed actively exploited (CISA KEV); the vendor-released fix is Froxlor 2.3.12.
Unauthenticated SQL injection in the joomlaboat.com YouTube Gallery extension for Joomla (versions below 5.7.3) lets remote attackers inject arbitrary SQL into read queries through the video search and sorting parameters of the public-facing gallery. No credentials, user interaction, or non-default configuration are required - only that the extension is installed and its video search/sorting front end is reachable, which is its normal deployment state. The CNA rates it 9.3 under CVSS 4.0, our independent assessment scores it as high severity with confidentiality impact dominant (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L), and no public exploit code or confirmed active exploitation was identified at time of analysis. Impact is bounded by deployment scope: core Joomla installations without this third-party extension are not affected, but any site that does run it is exposed to unauthenticated database disclosure.
Unauthenticated information disclosure in the Team Members WordPress plugin (versions through 9.2) lets remote attackers pull full team-member records - including email addresses and phone numbers - for entries the administrator never published. The plugin's AJAX action performs no authorization or visibility check, so an attacker only needs to reach the site's admin-ajax.php endpoint and enumerate record IDs; no login or user interaction is required (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, 5.3). Publicly available exploit code exists and the WPScan advisory is public, but there is no evidence of confirmed active exploitation (CISA SSVC exploitation: none) and EPSS is low at 0.14% (3rd percentile), consistent with a genuine but low-severity confidentiality issue whose impact is bounded by how many unpublished member records with contact details exist on a given site.
Stored cross-site scripting in Froxlor 2.0.0 through 2.3.10 lets an authenticated customer - the lowest-privileged account role - inject JavaScript through the issuer organization field of an SSL certificate they upload for their own domain, which is parsed by openssl_x509_parse() and stored verbatim without sanitization. The payload executes only when a reseller or administrator opens Domains > SSL certificates, because the table-listing renderer passes scalar cells through Twig's raw filter and disables HTML auto-escaping, so the script runs in the privileged user's session and can result in full administrator account takeover. Because a Froxlor admin controls webserver, DNS and PHP configuration applied by a root cron job, that takeover can be escalated to command execution as root on the managed server. No public exploit identified at time of analysis; exploitation requires a valid tenant account plus privileged-user page interaction (UI:P), which makes this a genuine priority within its deployment niche rather than a mass-exploitation emergency.
Unauthenticated path traversal in the lomart.fr UP extension for Joomla (versions 5.0.0 through 5.2.0 and 6.0.0 through 6.0.29) allows remote attackers to read files outside the intended plugin directory, exposing configuration files, credentials and other sensitive data under the web root's readable filesystem. The reported CVSS 4.0 score is 9.2, and the independently assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) confirms a confidentiality-only impact with no authentication or user interaction required, while integrity and availability remain unaffected. Real-world risk is governed by deployment scope rather than exploitability: this is a niche third-party Joomla extension, no public exploit was identified at time of analysis, and only sites that have the plugin installed and enabled at an affected version are exposed.
Authentication bypass in Flowise 3.1.4 and earlier running in Enterprise/platform mode with SSO enabled allows an attacker who can authenticate at any configured SSO provider while asserting a pending invitee's email address as the email claim to hijack that invitation, flipping the target account and its organization membership to ACTIVE without ever possessing the emailed invitation token. Our independent assessment scores it CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L (vendor CVSS 4.0 base 9.2), reflecting full confidentiality and integrity impact with high attack complexity driven by the need for a matching SSO identity; the practical limiting factor is the trust and email-verification behavior of the configured SSO provider, and exploitation is constrained to the invitation's validity window (24 hours by default). No public exploit code has been identified at time of analysis, and at the time of the advisory no patched version was available.
Unauthenticated account takeover of pending invited users in Budibase Server (@budibase/server) versions 3.41.0 through 3.45.0, caused by an authentication bypass in the OIDC/SSO login path. In sso.authenticate, when no existing user matches the incoming SSO subject, the server resolves pending invites using only the IdP-asserted email address, skipping both invite-code validation and the email_verified check (which guards only the existing-account lookup), so anyone who can register at a trusted IdP and claim a victim's invited email - even with email_verified=false - consumes the invite and inherits its privileges, including builder and admin.global roles. Impact scales with the outstanding invite: an admin.global invite yields full tenant compromise (all apps, datasources with production credentials, automations) and the invite is consumed, denying onboarding to the legitimate invitee. Exploitation requires OIDC/SSO configured against a trusted IdP and an unclaimed pending invite matching the asserted email, per the vendor's AT:P attack-requirement modifier; no public exploit code or confirmed active exploitation was identified at time of analysis, and CVSS 4.0 rates this 9.2 with a CVSS 3.1 equivalent of AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.
Account takeover in Flowise through 3.1.4 allows unauthenticated attackers to impersonate any existing user by claiming that user's email at any configured SSO provider. This authentication bypass (CWE-287) occurs because the application resolves users solely by email without storing provider or subject identifier bindings, enabling cross-provider or local-password claim of identities. Exploitation requires SSO to be enabled and knowledge of a victim's email, but no public exploit code has been identified at time of analysis.
Credential theft in OpenClaw for iOS (versions >= 2026.7.1 and < 2026.8.11) lets a man-in-the-middle attacker who redirects the same Gateway host and port and presents a certificate that passes iOS system trust capture the injected Gateway token or password from the authenticated Terminal and session Dashboard WebViews, which - unlike native connections - failed to enforce the saved Gateway TLS fingerprint. The stolen credential can grant operator access, including reading sensitive Gateway state and invoking host-capable tools. No public exploit has been identified at time of analysis, and exploitation requires a prior accepted Gateway fingerprint, a network-adjacent MITM position, a validly trusted certificate for the host, and the victim opening the affected WebView, which substantially limits realistic risk to targeted adversaries despite the vendor's Critical 9.0 CVSS 4.0 rating.
Server-side request forgery in OpenClaw (npm package 'openclaw') versions 2026.4.5 through before 2026.8.1 lets an attacker who controls an approved remote Chrome DevTools Protocol (CDP) hostname, or its DNS answers, use DNS rebinding to steer the Gateway into connecting to SSRF-denied destinations such as loopback, private, link-local, or cloud metadata addresses. The flaw is a check-then-use (TOCTOU) gap: the Gateway validates and pins DNS at configuration time, but the raw WebSocket and Playwright transports independently re-resolve the hostname when the connection is actually made, discarding the pin. Per the CVSS:3.1 assessment (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N) exploitation is unauthenticated but requires a non-default, operator-configured hostname-based remote CDP endpoint plus a successful rebinding race, so impact is bounded by the internal services reachable from the Gateway host; no public exploit is identified at time of analysis and CISA KEV does not list this issue.
Second-order SQL injection in Budibase Server (@budibase/server) before 3.45.0 can let an authenticated attacker with DDL rights on a connected MySQL or MSSQL datasource create a malicious column name that escapes identifier quoting, then execute injected SQL when a Budibase builder later renames that column through the UI. Because the MySQL connection is opened with multipleStatements:true in this default case, stacked statements can run as the datasource user and bypass Budibase's row/table permission model, enabling arbitrary reads, writes, or destructive operations. No public exploit identified at time of analysis; vendor-released patch: 3.45.0.
Unauthenticated remote attackers can use the January media proxy/embed service in stoatchat before 0.15.5 to probe the host filesystem and drain server resources. When January fetches an attacker-hosted resource served as image/svg+xml, the SVG <image href> values are resolved as local filesystem paths, so observable response-time differences reveal whether local files exist and supported local image files are disclosed after re-encoding, while unbounded reads of each referenced file generate large amounts of filesystem I/O and memory pressure (a published proof of concept drives roughly 4.34 GB of reads) causing denial of service. Publicly available exploit code exists, no authentication or user interaction is required, and the issue is fixed in version 0.15.5.
Privilege escalation in the WordPress plugin Groups - Memberships and Access Control (itthinx) affects all versions up to and including 4.6.0, allowing any authenticated Subscriber-level user to self-enroll in arbitrary groups - including privileged admin groups - and ultimately mint a group that grants every registered WordPress capability, reaching Administrator. The root cause is an authorization check in groups_join() that reads the ambient post's author capabilities ($post->post_author) instead of the acting user's, while the same response hands the caller a valid join hash and nonce; an attacker only needs valid low-privilege credentials and the post ID of any Administrator-authored post, supplied via the post_ID parameter of the authenticated wp_ajax_parse_media_shortcode AJAX handler, with no victim interaction. Per available intelligence there is no confirmed active exploitation (CISA KEV) and no public exploit code identified at time of analysis, though our independent assessment rates this a genuine high-priority issue rather than a high-CVSS-but-low-real-risk case, given the low bar of Subscriber self-registration on many sites.
A time-of-check time-of-use race condition in OpenClaw's OpenShell local mirror filesystem mutation operations (remove, mkdir, rename) before 2026.7.1 allows an authenticated local attacker to escape the sandbox and delete, create, or rename host filesystem paths outside the intended mirror root with the permissions of the OpenClaw process user. Exploitation requires winning a narrow timing race between the sandbox path-safety check and the actual operation, which is a non-trivial precondition, but it does not require the operator to have granted host filesystem access outside the sandbox, so default deployments are affected. No public exploit code or active exploitation has been identified at time of analysis; the vendor has released a fix in version 2026.7.1.
Remote code execution via arbitrary file write affects Budibase Server versions before 3.45.0. An authenticated attacker holding the BUILDER role can upload a crafted ZIP to the PWA icon upload endpoint that exploits missing symlink validation during extraction, using leaf symlink entries followed by duplicate file entries to overwrite arbitrary files as root. This allows root-level code execution; no public exploit code has been identified at time of analysis, and the vulnerability is not reported as actively exploited.
Unauthenticated information disclosure in the getgrav/grav-plugin-comments plugin (through 1.2.10) lets a remote attacker retrieve every comment posted to a Grav site in the last 7 days, including each commenter's email address and the absolute server filesystem path of the underlying data file, simply by sending a GET request to /admin/comments/page:<n> (for example page:0.001). The vulnerable admin handler performs its authorization check against isAdmin(), which only signals that the admin service is registered on the current route rather than that the visitor is authenticated, and it emits the JSON response and calls exit() during the plugins stage before the classic Admin plugin can render its login screen. Exploitation requires the site to run the classic Grav Admin plugin with the Comments plugin enabled (the default configuration), and is a genuine but bounded risk: no public exploit code has been identified at time of analysis, there is no CISA KEV listing, and the assessed impact is limited to confidentiality (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N), with no write or code-execution capability - the 8.7 CVSS 4.0 score published with the CVE reflects a higher-confidence confidentiality weighting than this assessment supports. The issue is fixed in 1.2.11.
Information disclosure in Grav CMS before 2.0.25 lets unauthenticated remote attackers read sensitive files - configuration secrets and account password hashes - when the site is served by Microsoft IIS using the bundled webserver-configs/web.config over a case-insensitive filesystem such as NTFS, simply by varying the case of a folder name or extension (for example GET /user/CONFIG/system.YAML) so that none of the case-sensitive URL Rewrite deny rules match. The practical blast radius is narrower than the raw path-bypass suggests: whether a bypassed file is actually returned depends on MIME registration, with .json served by default while .yaml/.yml return HTTP 404.3 on a stock IIS unless a YAML MIME mapping has been added; the equivalent gap in webserver-configs/lighttpd.conf is lower risk because lighttpd typically runs on case-sensitive filesystems, and deployments behind Apache (.htaccess), nginx, Caddy, or the PHP built-in server are not affected. No public exploit identified at time of analysis, and while the vendor-released patch is Grav 2.0.25, upgrading alone is insufficient because the .htaccess installer heal does not rewrite web.config or lighttpd.conf, so operators must manually re-copy the corrected sample files.
Symlink-following flaws in Hugo's theme and module mount confinement allow files outside a project's mount roots to be read during a site build and, via static mounts, published into the public/ output directory. The flaw affects Hugo builds after v0.123.0 and before v0.166.0 for any project that adopts an untrusted theme checked into themes/ or a vendored (non-Go-modules) module containing a symlink at a mount root and then runs a build; the vendor scores this 8.7 (High) under CVSS 4.0, while independent analysis models it as CVSS 3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N because the site operator must first adopt the malicious theme and execute the build. No public exploit code identified at time of analysis and no KEV listing; a vendor-released patch exists in v0.166.0.
GitPython before 3.1.62 is vulnerable to a path traversal (CWE-22) in Submodule.update() that allows unauthenticated remote attackers to create, populate from a submodule URL, and potentially delete directories outside the repository working tree when an application updates submodules at a non-HEAD (historical) commit. The flaw stems from the `path` field in an untrusted .gitmodules file being used without the _to_relative_path() containment guard that is applied in add() and move(). Exploitation requires an application flow that checks out submodules at a historical commit and an attacker-controlled repository; the standard clone-then-update flow re-derives the path from a canonical tree lookup and is not affected. No public exploit code or confirmed active exploitation (CISA KEV) exists at time of analysis, and the independent assessment rates real-world priority as low-to-medium despite the vendor's CVSS 4.0 score of 8.7.
Unbounded heap growth in Netty's HTTP/3 codec (io.netty:netty-codec-http3) 4.2.0.Final through 4.2.17.Final allows a remote, unauthenticated HTTP/3 client to exhaust server memory and cause a denial of service. The QpackEncoder retains per-stream encoder state indefinitely because entries are only released when the peer sends a Section Acknowledgment or Stream Cancellation instruction, not when the HTTP/3 stream completes; an attacker advertising a non-zero QPACK dynamic-table capacity and withholding those acknowledgments across sequential requests on a single QUIC connection can accumulate unbounded tracked streams, field sections, and bytes, bypassing concurrent-stream limits. No public exploit code has been identified at time of analysis, and no CISA KEV confirmation of active exploitation is present; the practical exposure is limited because Netty's HTTP/3 (QUIC) support is not yet widely enabled in production. Vendor-released patch: 4.2.18.Final (GHSA-495p-pchh-r4mc).
Unauthenticated remote attackers can delete every device registration in a Parse Server application - or any attacker-chosen subset - by submitting non-string (object) values in installation/device-token fields that are used to build the deduplication query without type validation. The only prerequisite is knowledge of the public application ID, which is intentionally distributed inside client apps; no account, session token, master key, or user interaction is required, and the destructive cleanup runs with elevated privileges before class-level permissions are evaluated. Parse Server versions prior to 8.6.90 and 9.0.0 through 9.10.1-alpha.9 are affected in the default configuration that exposes the REST API to clients and uses push notifications, and because deleted registrations cannot be recovered server-side, push delivery halts until every client re-registers; no public exploit identified at time of analysis, and the vendor-released patch is 8.6.90 or 9.10.1-alpha.9.
Arbitrary file read in Hugo v0.161.0 through v0.165.0 allows an attacker who can contribute content to a Hugo project - for example by opening a pull request - to commit a symlink such as assets/css/x.css pointing to /etc/passwd alongside a PostCSS plugin that reads it, causing any file readable by the build process to be disclosed and potentially published into the generated site. The flaw is remotely triggerable by unauthenticated attackers per the reported vector (PR:N), but in practice it only bites projects that actually invoke Node.js-based asset pipelines (css.PostCSS, css.TailwindCSS, js.Babel) under the default security configuration, and only when the attacker-supplied content is really built - automated CI or deploy-preview builds satisfy this with no human interaction, while review-then-merge workflows require a maintainer to build the change. Impact is confidentiality-only: there is no code execution or write primitive, and no public exploit identified at time of analysis; projects that never call the Node.js tools are unaffected.
Unbounded per-connection heap growth in Netty's HTTP/3 codec (io.netty:netty-codec-http3 4.2.0.Final-4.2.17.Final) allows an unauthenticated remote peer holding an established HTTP/3 connection to exhaust server memory and trigger OutOfMemoryError, resulting in denial of service. The QPACK encoder-stream handler (QpackEncoderHandler, installed by default on the peer-initiated unidirectional encoder stream, type 0x02) accepts an attacker-declared string-literal length of up to Integer.MAX_VALUE (~2 GiB) for the Name Length and Value Length fields of the 'Insert With Literal Name' instruction, then retains and grows the per-connection decode buffer while the peer trickles fewer bytes than declared; existing HTTP/3 limits such as maxHeaderListSize, maxUnknownFramePayloadLength, and DEFAULT_MAX_FIELD_SECTION_SIZE are not applied to this handler and provide no mitigation. Netty 4.2.18.Final resolves the issue, and no public exploit code was identified at time of analysis; the practical exposure is limited to services that have explicitly adopted Netty's opt-in HTTP/3 codec.
Remote denial of service in Netty's HTTP/3 codec (io.netty:netty-codec-http3) 4.2.0.Final through 4.2.17.Final lets an unauthenticated remote peer exhaust server memory and CPU by opening a QPACK unidirectional stream (type 0x02 encoder or 0x03 decoder) and sending an all-prefix-bits first byte followed by an endless run of 0x80 continuation bytes. Because QpackUtil.decodePrefixedInteger returns -1 ("need more bytes") without consuming input, the ByteToMessageDecoder cumulator grows without bound and each decode() call re-scans the whole accumulated buffer at O(N^2) CPU cost, producing unbounded per-connection heap growth (OutOfMemoryError) and event-loop starvation. Netty's own advisory states the flaw is reachable in every configuration with no special flag or non-default setting, and the assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) confirms an availability-only impact with no confidentiality or integrity exposure; no public exploit code or CISA KEV entry was identified at time of analysis, and vendor-released patch 4.2.18.Final is available.
OpenClaw (npm package 'openclaw') before 2026.7.1 lets an actor who can steer a tool-enabled agent create a persistent cron job that runs attacker-chosen commands with the privileges of the OpenClaw process user. A mixed-case payload 'kind' value slips past the agent-facing shell-execution guard and later normalizes into a command job, targeting the model-facing cron tool only. The vendor scores this 8.7 (High) on CVSS 4.0 (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H) and the vendor-released patch is 2026.7.1; no public exploit identified at time of analysis.
SQL injection in SiYuan's graph query endpoint, affecting all releases before v3.8.4, allows an unauthenticated remote attacker to read arbitrary database rows spanning every notebook on the instance. The issue is conditionally gated: it only becomes reachable when the deployment is running in published-site mode with authentication disabled, which is a non-default configuration - standard local single-user installs and published sites that retain authentication are not exposed. Impact is limited to confidentiality (read-out of stored notes and metadata) with no data modification or service disruption described, and no public exploit has been identified at time of analysis, though the vendor has released a fix.