Aillesim

The issue is a Stored Cross-Site Scripting problem due to insufficient input sanitization and output escaping, allowing authenticated attackers with administrator-level permissions and above to inject arbitrary web scripts in pages. This affects multi-site installations and installations where unfiltered html has been disabled.

The issue is related to Cross-Site Request Forgery due to missing or incorrect nonce validation on the `ajax()` function. This allows unauthenticated attackers to perform various actions related to managing pricing tables by tricking a site administrator into performing an action, such as clicking on a link.

The issue arises from a missing capability check on the `ajax()` function, allowing authenticated attackers with subscriber-level access and above to perform unauthorized actions, such as editing pricing tables.

Name of the Vulnerable Software and Affected Versions: Snippet Shortcodes plugin for WordPress versions up to, and including, 4.1.4 Description: The issue is due to missing or incorrect nonce validation when adding or editing shortcodes, making it possible for unauthenticated attackers to modify shortcodes via a forged request. This can be achieved if an attacker can trick a site administrator into performing an action, such as clicking on a link. Recommendations: For versions up to, and including, 4.1.4, update to a version higher than 4.1.4 to resolve the issue. As a temporary workaround, consider restricting access to shortcode editing and addition functionality to minimize the risk of exploitation.

Name of the Vulnerable Software and Affected Versions: Custom Product List Table plugin for WordPress versions up to, and including, 3.0.0 Description: The issue is due to missing or incorrect nonce validation when modifying products, making it possible for unauthenticated attackers to add, delete, bulk edit, approve, or cancel products via a forged request. This can happen if an attacker can trick a site administrator into performing an action, such as clicking on a link. Recommendations: For versions up to, and including, 3.0.0, update to a version that includes proper nonce validation to prevent Cross-Site Request Forgery attacks. As a temporary workaround, consider restricting access to product modification features to minimize the risk of exploitation.

The issue allows authenticated attackers with subscriber access or above to modify the plugin's settings due to a missing capability check on the `disable fe assets` function. Additionally, the lack of a nonce check results in a CSRF vulnerability, enabling attackers to change the plugin's settings without proper validation.

The issue is related to Stored Cross-Site Scripting via admin settings due to insufficient input sanitization and output escaping. This allows 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. The issue only affects multi-site installations and installations where unfiltered html has been disabled.

The issue is related to Stored Cross-Site Scripting via admin settings due to insufficient input sanitization and output escaping. This allows 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. The issue only affects multi-site installations and installations where unfiltered html has been disabled.

The issue is due to missing or incorrect nonce validation on several functions hooked to AJAX actions, making it possible for unauthenticated attackers to change slider titles, delete sliders, and modify plugin settings via a forged request. This can be achieved if an attacker can trick a site administrator into performing an action, such as clicking on a link.

The issue is related to Cross-Site Request Forgery. This occurs because the plugin improperly releases the tagged and patched version, using the vulnerable version as core files, while the patched version is included in a 'trunk' folder. This allows unauthenticated attackers to perform various actions via a forged request if they can trick a site administrator into performing an action, such as clicking on a link.

The issue allows authenticated attackers with subscriber access or above to modify data due to a missing capability check on several AJAX actions. This enables them to change plugin settings and perform other actions, such as deleting sliders.

The issue is related to Cross-Site Request Forgery due to missing or incorrect nonce validation on the `wptodo settings()` function. This allows unauthenticated attackers to modify the plugin's settings via a forged request if they can trick a site administrator into performing an action, such as clicking on a link.

The issue is due to missing or incorrect nonce validation on the `wptodo manage()` function, making it possible for unauthenticated attackers to add new todo items via a forged request. This can be achieved if an attacker can trick a site administrator into performing an action, such as clicking on a link.

The issue is related to Stored Cross-Site Scripting via admin settings due to insufficient input sanitization and output escaping. This allows 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. The issue only affects multi-site installations and installations where unfiltered html has been disabled.

The issue is related to Stored Cross-Site Scripting via admin settings due to insufficient input sanitization and output escaping. This allows 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. The issue only affects multi-site installations and installations where unfiltered html has been disabled.

The issue is related to Stored Cross-Site Scripting via the `slider title` parameter due to insufficient input sanitization and output escaping. This allows authenticated attackers, with subscriber access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Name of the Vulnerable Software and Affected Versions: WP To Do plugin versions up to, and including, 1.3.0 Description: The issue is related to a Cross-Site Request Forgery (CSRF) vulnerability due to missing or incorrect nonce validation on the `wptodo addcomment` function. This allows unauthenticated attackers to add comments to to do items via a forged request if they can trick a site administrator into performing an action, such as clicking on a link. Recommendations: For versions up to, and including, 1.3.0, update to a version that includes the fix for the nonce validation issue in the `wptodo addcomment` function. As a temporary workaround, consider restricting access to the `wptodo addcomment` function until a patch is available.

The issue is due to missing or incorrect nonce validation when saving plugin settings, making it possible for unauthenticated attackers to change the plugin's settings via a forged request. This can be achieved if an attacker can trick a site administrator into performing an action, such as clicking on a link.

The issue is related to Stored Cross-Site Scripting via admin settings due to insufficient input sanitization and output escaping. This allows 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. The issue only affects multi-site installations and installations where unfiltered html has been disabled.

The issue is related to Cross-Site Request Forgery due to missing or incorrect nonce validation on the plugin's AJAX actions. This allows unauthenticated attackers to create and duplicate posts, retrieve post content, and modify post taxonomy by tricking a site administrator into performing an action, such as clicking on a link.