Joshua Chan

**Name of the Vulnerable Software and Affected Versions** vcita Online Booking & Scheduling Calendar for WordPress by vcita versions through 4.5.2 **Description** The issue allows retrieval of embedded sensitive data due to the generation of error messages containing sensitive information. **Recommendations** For versions through 4.5.2, update to a version later than 4.5.2 to resolve the issue.

**Name of the Vulnerable Software and Affected Versions** AIO Performance Profiler, Monitor, Optimize, Compress & Debug versions 1.2 and earlier **Description** The issue is related to a Missing Authorization vulnerability, which allows exploitation of incorrectly configured access control security levels. **Recommendations** For versions 1.2 and earlier, update to a version that includes a fix for this issue, as no specific workaround is provided for these versions. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** DualCube MooWoodle versions n/a through 3.2.4 **Description** The issue allows the retrieval of embedded sensitive data due to the insertion of sensitive information into the log file. This problem affects DualCube MooWoodle, enabling the exposure of confidential data. **Recommendations** For versions n/a through 3.2.4, update to a version later than 3.2.4 to resolve the issue. As a temporary workaround, consider restricting access to the log file to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** WP Go Maps versions prior to 9.0.41 **Description** The issue is a Cross-Site Request Forgery (CSRF) vulnerability in WP Go Maps, formerly known as WP Google Maps. This vulnerability allows an attacker to trick a user into performing unintended actions on a web application that the user is authenticated to. **Recommendations** For versions prior to 9.0.41, update to version 9.0.41 or later to resolve the issue. As a temporary workaround, consider implementing additional security measures such as validating user requests and ensuring that all state-changing actions require a token that is verified by the server to prevent CSRF attacks.

**Name of the Vulnerable Software and Affected Versions** Wp-Scribd-List versions 1.2 and earlier **Description** The issue is related to a Cross-Site Request Forgery (CSRF) vulnerability in Capa Wp-Scribd-List, which allows Stored XSS. **Recommendations** For versions 1.2 and earlier, update to a version that fixes the Cross-Site Request Forgery (CSRF) vulnerability to prevent Stored XSS attacks. As a temporary workaround, consider disabling any functionality that may be exploited through CSRF until a patch is available.

**Name of the Vulnerable Software and Affected Versions** MarvinLabs WP PT-Viewer versions prior to 2.0.2 **Description** The issue is related to improper neutralization of input during web page generation, also known as 'Cross-site Scripting', which allows Reflected XSS. This enables an attacker to inject malicious scripts into the website, potentially leading to unauthorized actions or data theft. **Recommendations** For versions prior to 2.0.2, update to version 2.0.2 or later to resolve the issue. As a temporary workaround, consider restricting user input to minimize the risk of exploitation. Avoid using potentially vulnerable API endpoints until the issue is resolved.

**Name of the Vulnerable Software and Affected Versions** Tripetto WordPress form builder plugin versions through 8.0.5 **Description** The issue is related to improper neutralization of input during web page generation, also known as Cross-site Scripting. This allows for Stored XSS, where an attacker can inject malicious scripts into the website. The estimated number of potentially affected devices worldwide is not available. There is no information about real-world incidents where this issue was exploited. **Recommendations** For versions through 8.0.5, update to a version later than 8.0.5 to resolve the issue. As a temporary workaround, consider restricting access to the plugin until a patch is available.

**Name of the Vulnerable Software and Affected Versions** Optimize Your Campaigns – Google Shopping – Google Ads – Google Adwords plugin for WordPress versions up to, and including, 3.1 **Description** The issue is related to the public accessibility of the print php information.php file, which allows unauthenticated attackers to extract sensitive configuration data. This information can be used in further attacks. **Recommendations** For versions up to, and including, 3.1, consider restricting access to the print php information.php file as a temporary workaround until a patch is available.

Name of the Vulnerable Software and Affected Versions: MBE eShip versions n/a through 2.1.2 Description: The issue is a Cross-Site Request Forgery (CSRF) vulnerability, which allows Cross Site Request Forgery. Recommendations: For versions n/a through 2.1.2, update to a version that contains a fix for this issue, however at the moment, there is no information about a newer version that contains a fix for this vulnerability.

Name of the Vulnerable Software and Affected Versions: The Events Calendar Event Tickets versions prior to 5.11.0.4 Description: A Cross-Site Request Forgery (CSRF) issue allows unauthorized actions to be performed on behalf of a user. This issue may be exploited to perform actions without the user's knowledge or consent. Recommendations: For versions prior to 5.11.0.4, update to version 5.11.0.4 or later to resolve the issue. As a temporary workaround, consider implementing additional validation for requests to prevent unauthorized actions. Restrict access to sensitive functionality to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Accept Authorize.NET Payments Using Contact Form 7 plugin for WordPress versions up to, and including, 2.2 **Description** The issue allows unauthenticated attackers to extract configuration data via the cf7adn-info.php file, which can be used to aid in other attacks. This is possible due to an Information Exposure vulnerability in the plugin. **Recommendations** For versions up to, and including, 2.2, consider disabling access to the cf7adn-info.php file as a temporary workaround until a patch is available. Restricting access to this file can minimize the risk of exploitation. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

Name of the Vulnerable Software and Affected Versions: Sanjay Singh Negi Floating Video Player versions 1.0 and earlier Description: The issue is related to a Cross-Site Request Forgery (CSRF) vulnerability that allows Stored XSS. This means an attacker can trick a user into performing unintended actions on a web application, potentially leading to the execution of malicious scripts stored on the server. Recommendations: For Sanjay Singh Negi Floating Video Player versions 1.0 and earlier, update to a version that fixes the CSRF vulnerability to prevent Stored XSS attacks. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

Name of the Vulnerable Software and Affected Versions: WP-NERD Toolkit versions n/a through 1.1 Description: The issue is related to the exposure of sensitive system information to an unauthorized control sphere. This problem affects the WP-NERD Toolkit, allowing unauthorized access to confidential system information. Recommendations: For WP-NERD Toolkit versions n/a through 1.1, update to a version later than 1.1 to resolve the issue. At the moment, there is no information about other specific mitigation measures for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Crafthemes Demo Import plugin for WordPress versions up to, and including, 3.3 **Description** The issue is related to arbitrary file uploads due to missing file type validation in the `process uploaded files` function. This allows authenticated attackers with Administrator-level access and above to upload arbitrary files on the affected site's server, potentially making remote code execution possible. **Recommendations** For versions up to, and including, 3.3, update to a version that includes a fix for the missing file type validation in the `process uploaded files` function. As a temporary workaround, consider disabling the `process uploaded files` function until a patch is available.

Name of the Vulnerable Software and Affected Versions: Import Export For WooCommerce versions 1.5 and earlier Description: The issue allows for the unrestricted upload of files with dangerous types, enabling an attacker to upload a web shell to a web server. This can lead to further exploitation and potential system compromise. Recommendations: For versions 1.5 and earlier, update to a version that contains a fix for this issue. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Accept Stripe Payments Using Contact Form 7 plugin for WordPress versions up to, and including, 2.5 **Description** The issue allows unauthenticated attackers to extract configuration information through the cf7sa-info.php file, which returns phpinfo() data. This information can be leveraged in another attack. **Recommendations** For versions up to, and including, 2.5, consider removing or restricting access to the cf7sa-info.php file until a patch is available. As a temporary workaround, consider disabling the plugin until a fixed version is released. Restrict access to the plugin's configuration to minimize the risk of exploitation.

**Name of the Vulnerable Software and Affected Versions** Tips and Tricks HQ, wptipsntricks Stripe Payments versions through 2.0.79 **Description** The issue is related to a Missing Authorization vulnerability, allowing the exploitation of incorrectly configured access control security levels. This can be exploited in the Stripe Payments component of Tips and Tricks HQ, wptipsntricks. **Recommendations** For versions through 2.0.79, update to a version later than 2.0.79 to resolve the issue. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Advanced What should we write next about versions n/a through 1.0.3 **Description** The issue is a Cross-Site Request Forgery (CSRF) vulnerability that allows Stored XSS. This means an attacker can trick a user into performing unintended actions on a web application, and also store malicious scripts that can be executed by other users. **Recommendations** For versions n/a through 1.0.3, as a temporary workaround, consider disabling any functionality that may be exploited through CSRF or Stored XSS until a patch is available. Restrict access to sensitive areas of the application to minimize the risk of exploitation. Avoid using parameters that could be used to inject malicious scripts in affected API endpoints until the issue is resolved. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Multi Feed Reader versions prior to 2.2.4 **Description** The issue is related to a Cross-Site Request Forgery (CSRF) vulnerability that allows Stored XSS. This means an attacker can trick a user into performing unintended actions on a web application, potentially leading to the execution of malicious scripts stored on the server. **Recommendations** For versions prior to 2.2.4, update to a version that includes a fix for this issue. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Content Audit Exporter versions 1.1 and earlier **Description** The issue allows exposure of sensitive system information to an unauthorized control sphere, enabling the retrieval of embedded sensitive data. This is due to a vulnerability in the IDE Interactive Content Audit Exporter. **Recommendations** For versions 1.1 and earlier, update to a version that fixes this issue, as the current version allows unauthorized access to sensitive system information. At the moment, there is no information about a newer version that contains a fix for this vulnerability.