An unauthenticated remote code execution vulnerability exists in the Joomla Extension Easy File Uploader versions prior to 2.9.7. An attacker can upload a PHP-executable file to the Joomla web root using a single multipart POST request without requiring credentials or a CSRF token.
The All in One SEO – AI SEO Plugin for WordPress versions up to 5.0.5 contains a stored cross-site scripting (XSS) vulnerability via the 'name' parameter. Authenticated users with subscriber-level access or higher can inject malicious scripts that execute when other users view affected pages. Exploitation requires specific conditions including WordPress 6.6 or later with the Interactivity runtime and an administrator placing the AIOSEO breadcrumb on the author template.
A stored cross-site scripting (XSS) vulnerability exists in the Cool Plugins Conditional Fields for Elementor Form – Display Conditions plugin, affecting versions up to 1.7.7. This vulnerability involves improper neutralization of input during web page generation, which can lead to script injection.
A stored cross-site scripting (XSS) vulnerability exists in LeapWorx Premium Addons for Elementor up to version 4.11.118. This flaw allows improper neutralization of input during web page generation, potentially enabling attackers to inject malicious scripts. The vulnerability has a CVSS score of 6.5, indicating a medium severity level.
A stored cross-site scripting (XSS) vulnerability exists in WPExperts Gutena Forms (Contact Form, Survey Form, Feedback Form, Booking Form, and Custom Form Builder) up to version 2.1.1. This vulnerability allows improper neutralization of input during web page generation, potentially enabling attackers to inject malicious scripts. The vulnerability has a CVSS score of 6.5, indicating a medium severity level.
A vulnerability in AIOHTTP's WebSocket implementation allows attackers to bypass receive queue limits by sending many small or compressed messages. This can cause excessive memory consumption on the server or client side. The issue arises because the WebSocket reader continues parsing frames after the receive queue pauses the transport, and empty messages are not counted towards the queue size. The vulnerability is fixed in version 3.25.2_5.
AIOHTTP versions >=3.25.2_3 and <3.25.2_5 contain a vulnerability where decompressing concatenated compressed streams (gzip, deflate, or zstd) causes excessive CPU usage due to quadratic time complexity. This can lead to event loop blocking on servers or clients when processing specially crafted compressed payloads. The issue is fixed in version 3.25.2_5.
A vulnerability in AIOHTTP's pure-Python HTTP parser causes excessive memory consumption and duplicate processing of pipelined requests when the request queue is full and an upgrade request is declined. This occurs because buffered data is re-fed repeatedly, causing buffer growth and re-dispatching of already-handled requests. The issue affects versions from 3.25.2_3 up to but not including 3.25.2_5. A patch is available in version 3.25.2_5. Users relying on the pure-Python parser (e.g., with AIOHTTP_NO_EXTENSIONS) are impacted, while switching to the default C parser mitigates the issue.
AIOHTTP versions >=3.25.2_3 and <3.25.2_5 have a vulnerability where data received during an HTTP upgrade request (such as a WebSocket handshake) is buffered without limit until the handler completes. This can lead to unbounded memory consumption if an attacker streams large amounts of data behind the upgrade request. The issue is fixed in version 3.25.2_5.
AIOHTTP's WebSocket implementation contains an integer overflow vulnerability in the max_msg_size check within the C extension. This flaw allows an attacker to bypass the maximum message size limit by sending a specially crafted WebSocket message with a declared frame length near 2^63, causing unbounded memory consumption. The issue affects versions from 3.25.2_3 up to but not including 3.25.2_5. A fix is available in version 3.25.2_5. As a workaround, users can disable the C extension by setting AIOHTTP_NO_EXTENSIONS=1 to use the unaffected Python reader.
AIOHTTP versions >=3.25.2_3 and <3.25.2_5 contain a vulnerability where multipart parts encoded with base64 can bypass the client_max_size limit. This occurs because the BodyPartReader.read_chunk() method reads until the chunk length is a multiple of 4 without enforcing a byte limit, allowing excessive memory consumption or event loop blocking. The issue is fixed in version 3.25.2_5.
AIOHTTP's Request.post() method lacked a limit on the number of URL-encoded form fields, causing insertion of many repeated keys into a MultiDict to take quadratic time on the event loop. This can allow an attacker to block the event loop by sending a form POST with many fields within the default client_max_size. The issue affects versions from 3.25.2_3 up to but not including 3.25.2_5 and has been fixed in version 3.25.2_5.
AIOHTTP's client CookieJar component improperly parsed Set-Cookie headers, creating additional cookies from unrecognized name=value attributes without limiting the number of stored cookies. This flaw allows a malicious server to cause the client to store an excessive number of cookies, leading to very large Cookie headers and excessive memory and CPU usage on the client side.
AIOHTTP's Application.add_domain() function had a performance issue where using two or more wildcards (*) in a domain mask caused polynomial-time matching on long Host headers, leading to event loop stalls. This could be exploited by an attacker to stall the server by sending requests with long Host headers against such domain masks. The issue is fixed in version 3.25.2_5. A workaround is to use at most one wildcard in a domain mask.