qbee-agent is the device agent component of the qbee.io IoT device management platform. Prior to 2026.27, the privileged createFile helper followed attacker-controlled symbolic links during file creation. A local unprivileged user whose account is managed by the SSH Keys bundle could replace ~/.ssh with a link to /root/.ssh, causing the agent to write an authorized key for root. On systems using RAUC download mode with ineffective kernel symlink protection, the predictable /tmp/.bundle.raucb.part path could be linked to a system file and then overwritten or truncated during an update. A file-distribution destination beneath an attacker-controlled directory could similarly redirect the partial-download path so the agent changed ownership of a sensitive file. These vectors could result in root privilege escalation, arbitrary file modification, or denial of service. This issue is fixed in version 2026.27.
REBUILD 4.3.0 through 4.5.4 contains a privilege escalation vulnerability that allows low-privileged authenticated users to obtain a SYSTEM_USER token by requesting /commons/file-preview with an arbitrary src value. Attackers can read the leaked _csrfToken from the redirect Location header and send it as X-AuthToken to access the admin center and administrative APIs.
thirdweb Dashboard through commit 940b3745 contains an open redirect vulnerability that allows remote attackers to send users to arbitrary sites by supplying an unvalidated redirectUri parameter on the /pay/[id] payment link page. Attackers can distribute payment links with a malicious redirectUri that PayPageWidget opens via window.open after payment without noopener, enabling phishing and reverse tabnabbing of the payment page.
Tornado versions from 2.7 up to but not including 2.22_4 contain an open redirect vulnerability due to inconsistent URL parsing between browsers and Python's urllib. This discrepancy allows URLs starting with three or more slashes to be treated differently, leading to incomplete mitigation of a previous redirect vulnerability. The issue was addressed in version 2.22_4, which improves detection and fixes a regression from the prior fix.
The Quick Page/Post Redirect Plugin WordPress plugin before 5.2.4 was distributed with a hidden update mechanism that fetched Quick Page/Post Redirect Plugin WordPress plugin before 5.2.4 updates from its author's own server instead of WordPress.org, which was used to push a backdoored build to sites, allowing the attacker controlling that server to inject arbitrary content into pages and to deliver arbitrary code to affected sites.
Version 5.2.1, as published on WordPress.org, bundled the Quick Page/Post Redirect Plugin WordPress plugin before 5.2.4 Update Checker library (updater/ directory) configured to poll https://anadnet.com/updates/?action=get_metadata&slug=quick-pagepost-redirect-Quick Page/Post Redirect Plugin WordPress plugin before 5.2.4. In March 2021 that server delivered a modified 5.2.3 build, different from the 5.2.3 later published on WordPress.org, which kept the update channel and added a the_content filter that, for logged-out visitors on single posts and pages, fetched content from https://w.anadnet.com/bro/3/ (passing the site host, request URI and visitor User-Agent) and prepended the response to the post (observed serving SEO spam links to search engine crawlers). Because the version string matched a later WordPress.org release, affected sites were not offered a clean update until 5.2.4.
Indicators of compromise:
- Outbound requests to anadnet.com or w.anadnet.com
- An updater/ directory (Quick Page/Post Redirect Plugin WordPress plugin before 5.2.4 Update Checker, Puc v4p10) inside wp-content/Quick Page/Post Redirect Plugin WordPress plugin before 5.2.4/quick-pagepost-redirect-Quick Page/Post Redirect Plugin WordPress plugin before 5.2.4/
- The strings filter_the_content_in_the_main_loop, ppr_pro, QQQEND or w.anadnet.com in page_post_redirect_Quick Page/Post Redirect Plugin WordPress plugin before 5.2.4.php
- page_post_redirect_Quick Page/Post Redirect Plugin WordPress plugin before 5.2.4.php with MD5 ad717da18cf8a2b69899c0d7dafee05a (tampered 5.2.3)
Remediation: remove the Quick Page/Post Redirect Plugin WordPress plugin before 5.2.4 (it has been closed on WordPress.org), or at minimum reinstall the clean 5.2.4 from WordPress.org, delete any leftover updater/ directory, verify the files with "wp Quick Page/Post Redirect Plugin WordPress plugin before 5.2.4 verify-checksums quick-pagepost-redirect-Quick Page/Post Redirect Plugin WordPress plugin before 5.2.4", clear the opcode cache, and treat any site that ran the tampered build as potentially compromised.
sysPass versions 3.0.1 through 3.2.11 have an authentication bypass vulnerability that allows unauthenticated attackers to reinstall the application by sending a POST request to the install handler. This bypass occurs because the install handler does not verify if the application is already installed. Exploitation enables attackers to overwrite configuration files, redirect the application to an attacker-controlled database, create administrator accounts, and execute arbitrary commands via crafted serialized gadget chains.
Attackers exploited typographical errors in domain names related to 27 AI brands to distribute malware. They used 186 typosquatting domains to deliver malicious payloads such as PowerShell commands, Microsoft Store-signed browser hijacking applications, and search-hijacking extensions affecting nearly one million users. The infrastructure includes 211 entry domains mimicking banks, insurers, and enterprise software, employing traffic profiling and platform-specific lures. This technique, termed TypoPrompting, leverages common user mistakes to redirect legitimate AI tool access into malware infection vectors.
Nuxt is an open-source web development framework for Vue.js. Nuxt from 3.0.0 until 4.6.4, @nuxt/nitro-server from 3.20.0 until 4.6.4, and @nuxt/vite-server from 4.6.0 until 4.6.4, routeRules matching leaves an encoded slash (%2F) in the request path while a catch-all page such as app/pages/[...slug].vue or a custom multi-segment page route decodes it into a route parameter. The getRouteRules result is therefore incomplete, and an unauthenticated request can render the page without the redirect, headers, proxy, SSR, noScripts, appMiddleware, or appLayout rules configured for the decoded path. Protected content is resolved only when the page interprets the decoded parameter accordingly: a custom multi-segment parameter can contain the decoded path, while a repeatable catch-all must join the slash-containing array element; route.path remains encoded and does not resolve that resource. Static pages, single-segment parameters, server/api handlers, and server/routes handlers are not affected because they do not have the same encoded-path mismatch. This issue is fixed in version 4.6.4.
OpenEMR versions prior to 8.5.0 have a missing authorization vulnerability in the library/ajax/user_settings.php component. This flaw allows any authenticated user to persist arbitrary global configuration overrides by sending specially crafted POST requests. Attackers can redirect external service hosts such as CouchDB, eRx, phiMail, or SMTP to attacker-controlled servers, potentially leading to exfiltration of system credentials and patient protected health information (PHI).
Vvveb through 1.0.8.6 contains an SQL injection vulnerability because the @KEYS(:each) macro emits PHP array keys as backtick-quoted INSERT column names without escaping, and several procedures in admin/sql/mysqli/product.sql and admin_auth_token.sql omit the @FILTER guard. Authenticated back-office users able to save products can submit product_<feature> POST array keys containing backticks to redirect bound values into unexposed columns or break SQL statements.
The MISP Modules website component contains an open redirect vulnerability in its login endpoint. The /login route accepted a user-supplied next query parameter and passed it directly to Flask's redirect() function without validating the destination. An attacker could craft a URL such as https://victim-host/login?next=https://attacker.example/phish and deliver it to a user (e.g., via email or a lookalike page). After the user successfully authenticated, the application issued a 302 redirect to the attacker-controlled external URL. This enables phishing attacks where a user, believing they are still on the legitimate MISP Modules site, may enter additional credentials or sensitive information on the attacker's page. It can also be used to obscure the true destination of a link, bypassing user trust in the legitimate domain. The vulnerability requires the victim to interact with the crafted URL and complete a login, but no prior authentication or special configuration is needed on the attacker's side. The affected component is the website sub-project of misp-modules, specifically the account blueprint in website/app/account/account.py. No version boundaries are specified in the patch metadata.
A high-severity security vulnerability (CVE-2026-76184) affects Rundeck versions prior to 6.0.1-r11. The issue involves the Eclipse Jetty HttpClient component, which may improperly handle redirects of the form '/secure/'. This flaw has been assigned a CVSS 4.0 base score of 8.2, indicating a significant security risk. A fix is available in Rundeck version 6.0.1-r11.
A security vulnerability in the wso2am package involves Apache CXF’s OIDC relying-party component, which could redirect users to an attacker-controlled URL after successful authentication. This could lead to limited confidentiality and integrity impacts. The issue affects versions prior to 4.7.0-r4 and has been assigned CVE-2026-79650 with a medium severity rating.
SOGo versions prior to 5.12.13 have a vulnerability that allows authenticated users to inject arbitrary Sieve script directives. This occurs because unescaped notification address values are inserted into generated Sieve scripts, enabling attackers to embed redirect or discard statements. Such injection can bypass administrator-configured forwarding-domain constraints, potentially redirecting or discarding incoming mail.
Joomla / WordPress Extension - acymailing.com - Open redirect on the subscription and unsubscription endpoints in AcyMailing 1.0.0 - 11.1.1 - On a default configuration, an attacker can craft a link on the affected site that redirects the visitor to an arbitrary external site, which is usable for phishing under the trusted domain.