“ We take our security policies very seriously and apply them to all add-ons, whether hosted on AMO or not,” the company’s policy reads. It turns out that Mozilla doesn’t want extensions to execute remote codes anymore because of its potential threat to security and privacy. Expectedly, the blacklisting automatically killed the add-on in Firefox installation with the feature on.

However, Mozilla still put the extensions on the Bugzilla list. The policy change prompted developers to pull their extensions from the AMO, and offered them as unlisted add-ons to users. Self-hosted and read unlisted extensions, on the other hand, had no such restriction. That means developers that have their add-ons on AMO were not allowed to execute remote code. The problematic add-on plugin will be automatically disabled and no longer usable.” Mozilla’s Ban on Remote Code Execution Pluginsįor a while now, Mozilla has disallowed the execution of external remote code for listed extensions. “These add-ons violate Mozilla’s policies by executing remote code. Also, other affected extensions include Bridge Translate and Babelfox.

Two translation add-on developers, Google Translate this Page and Page Translator, confirmed that Mozilla banned their extension. This is especially true for plugins that inject codes from Bing Translate or Google Translate into the website to provide other language options.

According to recent reports, Mozilla has banned all remote code execution plugins in Firefox 72.Īlthough the Bugzilla listing mainly shows the extension ID, the ban seems to have affected several translation add-ons on the browser.

How to get firefox to translate a page