Fixmysite

HI, if there is nothing wrong with the code please can you contest it via Patchstack (https://patchstack.com/database/wordpress/plugin/hero-banner-ultimate/vulnerability/wordpress-hero-banner-ultimate-plugin-1-4-2-local-file-inclusion-vulnerability)? In the meantime we are getting security alerts about it which shows in our client reports so we’ll need to get it addressed or switch to another plugin. Obviously it would be in everyones best interest to get this resolved, let me know if you need help with testing or anything to help get this pushed through, many thanks in advance.

Hi,

It seems to be a conflict between your plugin and Yoast SEO Premium:

I get the following error when activating the “WooCommerce emerchantpay Payment Gateway Client” plugin:

Fatal error: Uncaught Error: Call to undefined function Automattic\Jetpack\wp_rand() in /wp-content/plugins/woocommerce/vendor/automattic/jetpack-a8c-mc-stats/src/class-a8c-mc-stats.php:161 Stack trace: #0 /wp-content/plugins/woocommerce/vendor/automattic/jetpack-a8c-mc-stats/src/class-a8c-mc-stats.php(99): Automattic\Jetpack\A8c_Mc_Stats->build_stats_url() #1 /wp-content/plugins/woocommerce/vendor/automattic/jetpack-a8c-mc-stats/src/class-a8c-mc-stats.php(124): Automattic\Jetpack\A8c_Mc_Stats->get_stats_urls() #2 /wp-content/plugins/woocommerce/includes/class-woocommerce.php(414): Automattic\Jetpack\A8c_Mc_Stats->do_server_side_stats() #3 [internal function]: WooCommerce->log_errors() #4 {main} thrown in /wp-content/plugins/woocommerce/vendor/automattic/jetpack-a8c-mc-stats/src/class-a8c-mc-stats.php on line 161

When “Yoast SEO Premium” is deactivated the error doesn’t show. However If I deactivate “Yoast SEO Premium”, activate “WooCommerce emerchantpay Payment Gateway Client”, then try to reactivate “Yoast SEO Premium” I get the following:

Plugin could not be activated because it triggered a fatal error. Fatal error: Uncaught Error: Call to undefined method Composer\Autoload\ClassLoader::setClassMapAuthoritative() in /wp-content/plugins/wordpress-seo-premium/vendor/composer/autoload_real.php:43 Stack trace: #0 /wp-content/plugins/wordpress-seo-premium/vendor/autoload.php(7): ComposerAutoloaderInit42a00a4ee82636814e937c49e791ee2d::getLoader() #1 /wp-content/plugins/wordpress-seo-premium/wp-seo-premium.php(67): require(‘…’) #2 /wp-admin/includes/plugin.php(2387): include_once(‘…’) #3 /wp-admin/plugins.php(194): plugin_sandbox_scrape() #4 {main} thrown in /wp-content/plugins/wordpress-seo-premium/vendor/composer/autoload_real.php on line 43

If there’s anything you can do including pointing me in the right direction please let me know, in the meantime I will contact Yoast.

Hi,

nothing on the domain was changed, the only other thing that changed since the issue appeared was that we updated the WP version from 6.5.5 – 6.6.

We are not using your plugin on this website so you can close this ticket but I thought it would be worth sharing in case there is a bug.. As mentioned the issue is resolved when deactivating the WP Code plugin and the site works fine when adding the same scripts to the head via the theme.

Hi, after changing invoice_number to number and invoice_date to date the pdfs stopped working and returned a fatal error:

Fatal error: Too few arguments to function WPO\WC\PDF_Invoices\Documents\Order_Document::number(), 0 passed in /themes/ico/woocommerce/pdf/iCO/invoice.php on line 119 and exactly 1 expected.

This is how the code is being used in the custom template:

            <?php if ( isset($this->settings['display_number']) ) { ?>

            <tr class="invoice-number">

                <th><?php echo $this->get_number_title(); ?></th>

                <td><?php $this->invoice_number(); ?></td>

            </tr>

            <?php } ?>

            <?php if ( isset($this->settings['display_date']) ) { ?>

            <tr class="invoice-date">

                <th><?php echo $this->get_date_title(); ?></th>

                <td><?php $this->invoice_date(); ?></td>

            </tr>

            <?php } ?>

Please can you confirm what needs changing so we are not using deprecations?