Vulnerabilities

Cross-Site Request Forgery (CSRF) vulnerability in Craig Hewitt Seriously Simple Podcasting seriously-simple-podcasting allows Cross Site Request Forgery.This issue affects Seriously Simple Podcasting: from n/a through

The ELEX WordPress HelpDesk & Customer Ticketing System plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.2.9 via the 'eh_crm_ticket_single_view_client' due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to read the contents of all support tickets.

The ELEX WordPress HelpDesk & Customer Ticketing System plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'eh_crm_remove_agent' function in all versions up to, and including, 3.3.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to remove the role and capabilities of any user with an Administrator, WSDesk Supervisor, or WSDesk Agents role.

The FluentCRM – Email Newsletter, Automation, Email Marketing, Email Campaigns, Optins, Leads, and CRM Solution plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'fluentcrm_content' shortcode in all versions up to, and including, 2.9.84 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> Revert "NFSD: Remove the cap on number of operations per NFSv4 COMPOUND"<br /> <br /> I&amp;#39;ve found that pynfs COMP6 now leaves the connection or lease in a<br /> strange state, which causes CLOSE9 to hang indefinitely. I&amp;#39;ve dug<br /> into it a little, but I haven&amp;#39;t been able to root-cause it yet.<br /> However, I bisected to commit 48aab1606fa8 ("NFSD: Remove the cap on<br /> number of operations per NFSv4 COMPOUND").<br /> <br /> Tianshuo Han also reports a potential vulnerability when decoding<br /> an NFSv4 COMPOUND. An attacker can place an arbitrarily large op<br /> count in the COMPOUND header, which results in:<br /> <br /> [ 51.410584] nfsd: vmalloc error: size 1209533382144, exceeds total<br /> pages, mode:0xdc0(GFP_KERNEL|__GFP_ZERO),<br /> nodemask=(null),cpuset=/,mems_allowed=0<br /> <br /> when NFSD attempts to allocate the COMPOUND op array.<br /> <br /> Let&amp;#39;s restore the operation-per-COMPOUND limit, but increased to 200<br /> for now.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ACPI: video: Fix use-after-free in acpi_video_switch_brightness()<br /> <br /> The switch_brightness_work delayed work accesses device-&gt;brightness<br /> and device-&gt;backlight, freed by acpi_video_dev_unregister_backlight()<br /> during device removal.<br /> <br /> If the work executes after acpi_video_bus_unregister_backlight()<br /> frees these resources, it causes a use-after-free when<br /> acpi_video_switch_brightness() dereferences device-&gt;brightness or<br /> device-&gt;backlight.<br /> <br /> Fix this by calling cancel_delayed_work_sync() for each device&amp;#39;s<br /> switch_brightness_work in acpi_video_bus_remove_notify_handler()<br /> after removing the notify handler that queues the work. This ensures<br /> the work completes before the memory is freed.<br /> <br /> [ rjw: Changelog edit ]

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> btrfs: fix memory leak of qgroup_list in btrfs_add_qgroup_relation<br /> <br /> When btrfs_add_qgroup_relation() is called with invalid qgroup levels<br /> (src &gt;= dst), the function returns -EINVAL directly without freeing the<br /> preallocated qgroup_list structure passed by the caller. This causes a<br /> memory leak because the caller unconditionally sets the pointer to NULL<br /> after the call, preventing any cleanup.<br /> <br /> The issue occurs because the level validation check happens before the<br /> mutex is acquired and before any error handling path that would free<br /> the prealloc pointer. On this early return, the cleanup code at the<br /> &amp;#39;out&amp;#39; label (which includes kfree(prealloc)) is never reached.<br /> <br /> In btrfs_ioctl_qgroup_assign(), the code pattern is:<br /> <br /> prealloc = kzalloc(sizeof(*prealloc), GFP_KERNEL);<br /> ret = btrfs_add_qgroup_relation(trans, sa-&gt;src, sa-&gt;dst, prealloc);<br /> prealloc = NULL; // Always set to NULL regardless of return value<br /> ...<br /> kfree(prealloc); // This becomes kfree(NULL), does nothing<br /> <br /> When the level check fails, &amp;#39;prealloc&amp;#39; is never freed by either the<br /> callee or the caller, resulting in a 64-byte memory leak per failed<br /> operation. This can be triggered repeatedly by an unprivileged user<br /> with access to a writable btrfs mount, potentially exhausting kernel<br /> memory.<br /> <br /> Fix this by freeing prealloc before the early return, ensuring prealloc<br /> is always freed on all error paths.

The Groundhogg — CRM, Newsletters, and Marketing Automation plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;term&amp;#39; parameter in all versions up to, and including, 4.2.6.1 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

The Magical Products Display plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;mpdpr_title_tag&amp;#39; and &amp;#39;mpdpr_subtitle_tag&amp;#39; parameters in the MPD Pricing Table widget in all versions up to, and including, 1.1.29 due to insufficient input sanitization and output escaping on user-supplied HTML tag names. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

The WP Directory Kit plugin for WordPress is vulnerable to SQL Injection via the &amp;#39;columns_search&amp;#39; parameter of the select_2_ajax() function in all versions up to, and including, 1.4.3 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

The Simple User Registration plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the &amp;#39;wpr_admin_msg&amp;#39; parameter in all versions up to, and including, 6.6 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

The WP Delete Post Copies plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 6.0.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.