Tealthcopter

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

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

The issue is related to Full Path Disclosure, which occurs due to the presence of a publicly accessible composer-setup.php file with error display enabled. This allows unauthenticated attackers to retrieve the full path of the web application, potentially aiding other attacks. However, the disclosed information is not useful on its own and requires another vulnerability to be present to cause damage to an affected website.

The issue allows authenticated attackers with Contributor-level access and above to include and execute arbitrary files on the server. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included. The vulnerability is related to Local File Inclusion via several widgets.

The issue allows unauthenticated attackers to view any item created in Elementor, such as posts, pages, and templates, including drafts, trashed, and private items, due to a missing capability check on the `get megamenu content()` function.

The issue is related to Cross-Site Request Forgery due to missing or incorrect nonce validation on the `wpr filter woo products` function. This allows unauthenticated attackers to inject malicious web scripts via a forged request if they can trick a site administrator into performing an action such as clicking on a link.

The vulnerability is due to the `/vendor/cocur/slugify/bin/generate-default.php` file being directly accessible and triggering an error, making it possible for unauthenticated attackers to retrieve the full path of the web application. This information can be used to aid other attacks, but it is not useful on its own and requires another vulnerability to be present for damage to an affected website.

The issue concerns the `/inc/bycwooodt get all orders.php` file being publicly accessible and generating a publicly visible error message. This allows unauthenticated attackers to retrieve the full path of the web application, which can be used to aid other attacks. The information displayed is not useful on its own and requires another vulnerability to be present for damage to an affected website.

The issue is related to the lack of file type validation in the `storeUploads` function, which allows authenticated attackers with Contributor-level access and above to upload arbitrary files on the affected site's server. This may make remote code execution possible. Approximately 80,000 WordPress sites are potentially at risk.

The issue is related to Full Path Disclosure, which occurs due to the `/vendor/aura/payload-interface/phpunit.php` file being publicly accessible and displaying error messages. This allows unauthenticated attackers to retrieve the full path of the web application, potentially aiding other attacks. However, the information displayed is not useful on its own and requires another vulnerability to be present for damage to an affected website.

The issue allows authenticated attackers with Contributor-level access and above to read the contents of arbitrary files on the server, which can contain sensitive information, via the inline SVG feature.

The issue allows authenticated attackers with Contributor-level access and above to inject arbitrary web scripts in pages. This is due to insufficient input sanitization and output escaping, making it possible for attackers to execute scripts whenever a user accesses an injected page.

The JetElements plugin for WordPress is vulnerable to Stored Cross-Site Scripting via several widgets 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.

The issue is related to the `/inc/class/fnm/export.php` file being publicly accessible with error logging enabled. This allows unauthenticated attackers to retrieve the full path of the web application, which can be used to aid other attacks. The information displayed is not useful on its own and requires another vulnerability to be present for damage to an affected website.

The issue is related to Stored Cross-Site Scripting via the plugin's custom JS functionality due to insufficient input sanitization and output escaping on user-supplied attributes. This allows 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 issue is due to missing or incorrect nonce validation on the `wpr filter grid posts()` function, making it possible for unauthenticated attackers to inject malicious web scripts via a forged request. This can happen if attackers can trick a site administrator into performing an action such as clicking on a link.

The issue arises from a missing capability check on the `tp install()` function, allowing unauthenticated attackers to install and activate arbitrary plugins. This can lead to remote code execution if another vulnerable plugin is installed and activated. The vulnerability was partially patched in version 1.1.1.

The issue is related to a missing capability check on the `vcita save user data callback()` function, allowing authenticated attackers with Subscriber-level access and above to inject malicious web scripts and update settings. This vulnerability can be exploited to modify data unauthorizedly.

The issue is related to Stored Cross-Site Scripting via a malicious display name due to insufficient input sanitization and output escaping. This allows 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 issue is related to Stored Cross-Site Scripting via the `template-post-custom-field` block due to insufficient input sanitization and output escaping. This allows authenticated attackers with Contributor-level access and above to inject arbitrary web scripts in pages, which will execute whenever a user accesses an injected page.