Description
The most powerful affiliate plugin for WordPress – Create professional affiliate websites with Amazon, eBay, AWIN, and 20+ other networks. Build comparison tables, import products automatically, and monetize your content with ease.
affiliate-toolkit is the perfect solution for bloggers, niche site owners, and affiliate marketers who want to create professional product presentations without coding. Use our modern templates, powerful import features, and extensive customization options to build your affiliate business.
🚀 Key Highlights:
* Multi-Network Support – Connect to Amazon, eBay, AWIN, CSV feeds, and many more
* Flexible Templates – 20+ ready-to-use templates for product boxes, comparison tables, lists
* Smart Import – Bulk import products, bestseller lists, and search results
* 100% Cache Compatible – Works perfectly with WP Rocket, W3 Total Cache, and more
* Gutenberg & Classic Editor – Full support for both editors
📚 Resources:
* Plugin Homepage
* Documentation & Tutorials
* Support Tickets
Core Features (Free):
Product Management
* Visual shortcode generator with live preview
* Import products individually or in bulk
* Search and filter products from backend
* Manual product creation with custom data
* Product categories and taxonomies
* Multiple product variations support
Display & Templates
* 50+ professional templates included
* Product boxes, comparison tables, and lists
* Fully responsive and mobile-optimized
* Custom template editor with Blade syntax
* Template import/export functionality
* Customizable colors, fonts, and styles
Amazon Integration
* Amazon Product Advertising API 5.0 support
* Import via ASIN, keyword, or bestseller lists
* All 17 Amazon marketplaces supported
* Automatic price and availability updates
* Amazon No-API mode available (addon)
Performance & Compatibility
* 100% compatible with all caching plugins
* Lazy loading and AJAX support
* Image proxy for faster loading
* Works with Gutenberg and Classic Editor
* Multisite support
* HTTPS/SSL ready
Premium Extensions:
🤖 AI Assistant [Coming Soon]
* AI-powered content generation (titles, descriptions, pros/cons)
* Automatic product scoring and quality analysis
* SEO-optimized alt text generation
* AI template generator with natural language
* Support for OpenAI GPT-4 and Anthropic Claude
📊 Price History (Learn more)
* Track and display price changes over time
* Beautiful price history charts
* Price drop notifications
* Historical data analysis
🔍 Frontend Search and Filter (Learn more)
* Live product search for frontend
* AJAX-powered instant results
* Customizable search widgets
* Filter by category, price, rating
📋 Comparison Tables (Learn more)
* Create professional comparison tables
* Side-by-side product comparisons
* Custom fields and attributes
* Mobile-responsive tables
🛍️ WooCommerce Connector (Learn more)
* Sync affiliate products with WooCommerce
* Use WooCommerce checkout for external products
* Combine physical and affiliate products
🌍 Geolocation (Learn more)
* Show products based on visitor’s location
* Automatic currency conversion
* Country-specific affiliate links
* IP-based redirection
📱 Product Pages (Learn more)
* Create dedicated product landing pages
* Custom page templates
* SEO-optimized product pages
* Full design control
📋 Import Sets (Learn more)
* Manage multiple import configurations
* Schedule different import tasks
* Organize imports by category or campaign
* Batch processing for large datasets
📤 Field Export (Learn more)
* Export product data to CSV
* Custom field selection
* Bulk data management
* Integration with third-party tools
🎨 Template Packs (Learn more)
* Premium template collections
* Industry-specific designs
* Conversion-optimized layouts
* Regular new template releases
⚙️ Custom Fields (Learn more)
* Add unlimited custom product fields
* Custom taxonomies and attributes
* Advanced filtering options
* Flexible data structure
📄 XML Import [Coming Soon]
* Import from XML feeds
* Support for various XML formats
* Automatic field mapping
* Scheduled XML imports
🧱 Gutenberg Blocks
* Native Gutenberg blocks for products and lists
* Drag-and-drop interface with live preview
* Inline product and list selection
* Direct product import from shops
* Block-based content editing
* Full German translation support
🔗 Network Connectors
* eBay Product API (Learn more)
* AWIN Product Feed (Learn more)
* Geizhals.at (Learn more)
* Billiger.de (Learn more)
* TradeDoubler (Learn more)
* Tracedelight
* Yadore (Learn more)
* Belboon, Commission Junction (CJ) and other networks via CSV feed
* and more
🎨 Compatibility Modes
* ASA 1 & ASA 2 compatibility (free addon)
* AAWP compatibility (free addon)
* Amazon Site Stripe replacement (free addon)
Supported Affiliate Networks:
Amazon (17 countries), eBay, AWIN, Commission Junction, Geizhals, Billiger.de, TradeDoubler, Tracedelight, Yadore, Belboon, Custom CSV Feeds
Supported Countries (Amazon):
🌍 Australia, Belgium, Brazil, Canada, China, Egypt, France, Germany, India, Italy, Japan, Mexico, Netherlands, Poland, Saudi Arabia, Singapore, Spain, Sweden, Turkey, United Arab Emirates, United Kingdom, USA
Supported languages:
- German
- English
- Translatable with *.po files
Need more features?
Search in our extensions and download the extensions you need. Upload the extension as plugin and activate it.
Our free and premium extensions:
https://www.affiliate-toolkit.com/extensions/
Get affiliate-toolkit now: https://www.affiliate-toolkit.com/pricing/
German/Deutsch
Das leistungsstärkste Affiliate-Plugin für WordPress – Erstelle professionelle Affiliate-Websites mit Amazon, eBay, AWIN und über 20 weiteren Netzwerken. Erstelle Vergleichstabellen, importiere Produkte automatisch und monetarisiere deinen Content mit Leichtigkeit.
affiliate-toolkit ist die perfekte Lösung für Blogger, Nischenwebsites und Affiliate-Marketer, die professionelle Produktpräsentationen ohne Programmierung erstellen möchten. Nutze unsere modernen Templates, leistungsstarke Import-Funktionen und umfangreiche Anpassungsoptionen für dein Affiliate-Business.
🚀 Highlights:
* Multi-Netzwerk-Support – Verbinde Amazon, eBay, AWIN, CSV-Feeds und viele mehr
* Flexible Templates – 20+ einsatzbereite Templates für Produktboxen, Vergleichstabellen, Listen
* Smart Import – Massenimport von Produkten, Bestseller-Listen und Suchergebnissen
* 100% Cache-kompatibel – Funktioniert perfekt mit WP Rocket, W3 Total Cache und mehr
* Gutenberg & Classic Editor – Volle Unterstützung für beide Editoren
📚 Ressourcen:
* Plugin Homepage
* Dokumentation & Tutorials
* Support Tickets
Kernfunktionen (Kostenlos):
Produktverwaltung
* Visueller Shortcode-Generator mit intuitiver Oberfläche
* Einzel- oder Massenimport von Produkten
* Suchen und Filtern von Produkten im Backend
* Manuelle Produkterstellung mit individuellen Daten
* Produktkategorien und Taxonomien
* Unterstützung für mehrere Produktvarianten
Darstellung & Templates
* Über 20 professionelle Templates inklusive
* Produktboxen, Vergleichstabellen und Listen
* Vollständig responsive und mobil-optimiert
* Custom Template Editor mit Blade-Syntax
* Template Import/Export Funktionalität
* Anpassbare Farben, Schriften und Stile
Amazon-Integration
* Amazon Product Advertising API 5.0 Support
* Import via ASIN, Keyword oder Bestseller-Listen
* Alle 17 Amazon-Marktplätze unterstützt
* Automatische Preis- und Verfügbarkeitsaktualisierungen
* Amazon No-API Modus verfügbar (Addon)
Performance & Kompatibilität
* 100% kompatibel mit allen Caching-Plugins
* Lazy Loading und AJAX-Support
* Bild-Proxy für schnelleres Laden
* Funktioniert mit Gutenberg und Classic Editor
* Multisite-Unterstützung
* HTTPS/SSL ready
Premium-Erweiterungen:
🤖 AI Assistant [Bald verfügbar]
* KI-gestützte Content-Generierung (Titel, Beschreibungen, Pro/Contra)
* Automatische Produktbewertung und Qualitätsanalyse
* SEO-optimierte Alt-Text-Generierung
* KI Template Generator mit natürlicher Sprache
* Unterstützung für OpenAI GPT-4 und Anthropic Claude
📊 Price History (Mehr erfahren)
* Verfolge und zeige Preisänderungen über die Zeit
* Wunderschöne Preisverlaufs-Diagramme
* Preissenkungsbenachrichtigungen
* Historische Datenanalyse
🔍 Frontend Suche & Filter (Mehr erfahren)
* Live-Produktsuche für das Frontend
* AJAX-gestützte Sofortergebnisse
* Anpassbare Such-Widgets
* Filter nach Kategorie, Preis, Bewertung
📋 Vergleichstabellen (Mehr erfahren)
* Erstelle professionelle Vergleichstabellen
* Produkte nebeneinander vergleichen
* Individuelle Felder und Attribute
* Mobile-responsive Tabellen
🛍️ WooCommerce Connector (Mehr erfahren)
* Synchronisiere Affiliate-Produkte mit WooCommerce
* Nutze WooCommerce-Checkout für externe Produkte
* Kombiniere physische und Affiliate-Produkte
🌍 Geolocation (Mehr erfahren)
* Zeige Produkte basierend auf Besucherstandort
* Automatische Währungsumrechnung
* Länderspezifische Affiliate-Links
* IP-basierte Weiterleitung
📱 Product Pages (Mehr erfahren)
* Erstelle dedizierte Produkt-Landing-Pages
* Custom Page Templates
* SEO-optimierte Produktseiten
* Volle Design-Kontrolle
📋 Import Sets (Mehr erfahren)
* Verwalte mehrere Import-Konfigurationen
* Plane unterschiedliche Import-Aufgaben
* Organisiere Imports nach Kategorie oder Kampagne
* Batch-Verarbeitung für große Datenmengen
📤 Field Export (Mehr erfahren)
* Exportiere Produktdaten nach CSV
* Individuelle Feldauswahl
* Massendatenverwaltung
* Integration mit Tools von Drittanbietern
🎨 Template Packs (Mehr erfahren)
* Premium Template-Sammlungen
* Branchenspezifische Designs
* Conversion-optimierte Layouts
* Regelmäßig neue Template-Releases
⚙️ Custom Fields (Mehr erfahren)
* Füge unbegrenzte individuelle Produktfelder hinzu
* Custom Taxonomien und Attribute
* Erweiterte Filteroptionen
* Flexible Datenstruktur
📄 XML Import [Bald verfügbar]
* Import aus XML-Feeds
* Unterstützung verschiedener XML-Formate
* Automatisches Feld-Mapping
* Geplante XML-Imports
🧱 Gutenberg Blocks
* Native Gutenberg-Blöcke für Produkte und Listen
* Drag-and-Drop Interface
* Live-Vorschau im Editor
* Block-Templates und Patterns
🔗 Netzwerk-Konnektoren
* eBay Product API (Mehr erfahren)
* AWIN Product Feed (Mehr erfahren)
* Geizhals.at (Mehr erfahren)
* Billiger.de (Mehr erfahren)
* TradeDoubler (Mehr erfahren)
* Tracedelight
* Yadore (Mehr erfahren)
* Belboon, Commission Junction (CJ) und andere Netzwerke via CSV Feed
* und mehr
🎨 Kompatibilitätsmodi
* ASA 1 & ASA 2 Kompatibilität (kostenloses Addon)
* AAWP Kompatibilität (kostenloses Addon)
* Amazon Site Stripe Ersatz (kostenloses Addon)
Unterstützte Affiliate-Netzwerke:
Amazon (17 Länder), eBay, AWIN, Commission Junction, Geizhals, Billiger.de, TradeDoubler, Tracedelight, Yadore, Belboon, Custom CSV Feeds
Unterstützte Länder (Amazon):
🌍 Australien, Belgien, Brasilien, China, Deutschland, Ägypten, Frankreich, Indien, Italien, Japan, Kanada, Mexiko, Niederlande, Polen, Saudi-Arabien, Schweden, Singapur, Spanien, Türkei, Vereinigte Arabische Emirate, Vereinigtes Königreich, USA
Unterstützte Sprachen:
- Deutsch
- Englisch
- Übersetzbar mit *.po-Dateien
Benötigst du weitere Funktionen?
Durchsuche unsere Erweiterungen und lade die gewünschten Erweiterungen herunter. Die Erweiterung kannst du einfach als Plugin hochladen und aktivieren.
Unsere kostenlosen und Premium-Erweiterungen:
https://www.affiliate-toolkit.com/de/erweiterungen/
Hol dir das Affiliate-Toolkit jetzt: https://www.affiliate-toolkit.com/de/preise/
Installation
- Upload the plugin via Plugins → Add New → Upload Plugin or extract the zip file into the
wp-content/plugins/directory. - Activate the plugin from the Plugins page.
- Navigate to affiliate-toolkit → Shops and create a new shop (e.g. Amazon with Creator API).
- Import products via affiliate-toolkit → Products → Import or create them manually.
- Display products in your posts or pages using the Gutenberg product box block or the shortcode generator.
FAQ
Is the plugin completely free?
Yes, the core plugin is completely free and includes product management, templates, and Amazon integration.
What if I need more features?
Premium extensions for additional networks (AWIN, eBay, CJ, etc.), AI content generation, price history, and more are available at affiliate-toolkit.com.
Do I need an Amazon API key?
No. You can use the Amazon Creator API or the No-API mode to import products without the traditional Product Advertising API. However, using the PA-API gives you access to more product data and automatic updates.
Which affiliate networks are supported?
The free version supports Amazon. With premium extensions you can connect to AWIN, eBay, Commission Junction, Tradedoubler, and 20+ other networks, or import products via CSV feeds.
Does the plugin work with my theme?
Yes, affiliate-toolkit is designed to work with any WordPress theme. All templates are fully responsive and adapt to your theme’s styling.
Is the plugin compatible with caching plugins?
Yes, it works with all major caching plugins including WP Rocket, W3 Total Cache, WP Super Cache, and LiteSpeed Cache.
Can I use the plugin with Gutenberg?
Yes, affiliate-toolkit provides a dedicated Gutenberg block for displaying product boxes directly in the block editor. You can also use shortcodes in any editor.
How do I display products on my site?
After importing products, you can display them using the Gutenberg product box block or the shortcode generator. The shortcode generator lets you choose from different templates and search for products directly.
Screenshots
Changelog
3.9.4
- FIX: The cronjob could loop endlessly on a single queue entry. The entry is taken out of “prepared” by writing its result back, but WordPress refuses a write completely when a value does not fit its column – and the error message of a failed CSV download contains the whole feed url, which exceeded the 700 characters of the message column. The status was never stored, the same entry was fetched again, and the feed was downloaded over and over: via cronjob url until the server aborted the request, via WP-CLI without end. The message column now holds a long text, values are shortened to the actual column length before they are written, a rejected write is retried with a reduced message, and the queue processing additionally stops a batch that comes back unprocessed twice and marks it as an error.
- FIX: A product whose data did not fit the columns of the internal tables was dropped completely and without a message, because WordPress refuses the whole write instead of shortening a single value. Affected were long product titles, long tracking urls and in particular the variation name, which is stored serialized but had only 250 characters available. The existing second attempt only removed unusual characters, not the length, so the product was simply missing from the list or kept its previous data. Values are now shortened to the actual length of their column before they are written; the serialized columns are left empty instead of being shortened, because a shortened serialized value can no longer be read back. The variation name now holds a long text.
- FIX: Any change to the structure of the list table would have failed, because its two indexes were created with an unconditional ALTER TABLE and a second run ends with “Duplicate key name”. They are now only created when they are missing, as in the product table.
- SECURITY: Removed the file-writing branch from the discount-notice handler. ATKP_StoreController::get_product_discounts() fetches the current promotion from affiliate-toolkit.com (wp-json/affiliate-toolkit/v1/aktion) and, when the response carried an “aktion_filename” and “aktion_filecontent”, wrote that content verbatim into the uploads directory with file_put_contents() – a response from the store could therefore place an arbitrary file, including executable PHP, into the installation. The store no longer sends those fields, and the handler now only decodes and caches the promotion text; the file write is gone. The notice continues to show the promotion as before.
- SECURITY: The discount-notice and add-ons feed requests to affiliate-toolkit.com now verify the TLS certificate (sslverify was false). With the file write already removed this was no longer a code-execution risk, but there is no reason to skip certificate verification for these feeds, so it is on now.
- FIX: The “Medium image” entry in the template editor’s toolbar inserted get_mediumimage($product), but that formatter method did not exist (it was misspelled get_mediumnimage), so any template using it stopped with a fatal error. Both spellings now work, so existing templates keep working.
- FIX: Product boxes and lists could show “Price:” with no value when the shop’s currency was set to “Format from merchant”. The formatter used the base price instead of the sale price as the merchant-formatted value, because get_saleprice_fallback() and get_baseprice_fallback() returned each other’s value. Both now return the right value, and if the merchant sends no formatted price, the plain number is shown.
- FIX: For products with variations, the shipping cost of the first variation was never read because of a typo in the field name. Shipping and total price are now correct for these products.
- FIX: In the price comparison, offers with the same shop title, price and shipping were not merged when “group shops” is enabled, because the comma removal in the title was written the wrong way round. Duplicate offers are now merged as intended.
- FIX: Fetching a product’s image gallery without the main image (get_images($product, false)) caused PHP warnings, and missing image sizes were not filled in from the main image. The main image is now always used as the fallback.
- FIX: The shop sort order (“Sort order” on the shop) was ignored in the price comparison unless one of the “Main product and …” sort modes was selected, because of an operator precedence error. It now applies in every sort mode, and in “Main product and …” modes the main product’s shop stays first.
- FIX: Functions like atkp_get_product() and the product box helpers could throw a TypeError when given a product or list id that does not exist. They now return an empty result instead.
- FIX: The price trend text (get_minpricedays) was hard-coded in German, measured “constant for N days” from a fixed date in 2010, and could read past the end of the price history. It now compares against the shop’s actual price history, shows the old and new price formatted in the shop’s currency, and is translatable English with German translations included.
- FIX: The “Import product” search in the shortcode generator always failed with an error, because the server checked a security token (nonce) under a different name than the one the generator sends. The same search in the Gutenberg product and list blocks sent no token at all. Searching a shop and importing a product from the generator and from the blocks works again.
- FIX: The live preview in the template editor always showed “invalid nounce” instead of the rendered template, because the preview request did not send its security token. The preview renders again.
- FIX: The template editor showed plain text fields without syntax highlighting and threw a JavaScript error, because it looked for a CodeMirror version that WordPress no longer loads. It now uses the editor bundled with WordPress. If syntax highlighting is turned off in your user profile, the plain text fields keep working, including inserting placeholders from the template bar.
- FIX: The “Custom fields” and “ACF fields” menus of the template bar showed raw HTML code instead of clickable entries, because the links were escaped a second time. The entries can be inserted into the template again.
- FIX: On a fresh installation, link tracking, the image gallery and the slider did not work until the settings had been saved once. Until then the plugin’s inline script was attached to a script that WordPress never loaded, so it was silently dropped. The script is now always output.
- FIX: The external cron URL returned HTTP 200 for a wrong key or a deactivated external cronjob, so monitoring tools did not notice the problem. It now returns 401 and 404. The cron error page also no longer shows server file paths, error messages and stack traces to anyone who opens the URL. These details now only appear on the command line or with WP_DEBUG, and are always written to the PHP error log.
- FIX: The cronjob status on the settings page always told WordPress-cron users to check a server-side cronjob, because the cron type was compared with a number instead of “wpcron”. WordPress-cron users now get the matching hint to save the settings page and re-register the scheduler.
- FIX: Importing a product by EAN through a shortcode (e.g. [atkp_product ean=”…”]) did not find an existing product with that EAN and could create a duplicate, because the EAN was never passed to the duplicate check. A product or list imported automatically by [atkp_product asin/ean=”…”] or [atkp_list keyword=”…”] was also not displayed on the first page view, because the new post id was read from the wrong place.
- FIX: The bit.ly link shortener could not work. When shop links were refreshed, the API key was passed in place of the url, and empty links caused a PHP TypeError. Links are now shortened with the correct values, and empty links are skipped.
- FIX: The shortcode generator and the Gutenberg product block showed German texts (e.g. “Importieren”, “Fehler bei der Suche”, “Produkt bearbeiten”, “Ausgabe wird im Frontend gerendert”) in English backends. All of these texts are now English and translatable, with German translations included.
- FIX: The help and warning texts on the settings pages were always shown in English, because display_helptext() and display_warntext() never passed them through the translation. They are now translated.
- FIX: The “not found” messages for shops and templates said “No lists found”, and the debug page labelled the button that recreates the product table “Drop & create list table”. Both texts are corrected.
- FIX: The default price colour of templates was the invalid value “#00000” (five digits), so browsers ignored it. It is now “#000000”. The default button size “mormal” was corrected to “normal” (the output is unchanged).
- FIX: On a fresh installation the “Main product selector” setting showed “Main product and Price” while “Price + Shipping cost” was actually used. The form now shows the setting that is really in effect.
- FIX: The misspelled post type argument publicly_queriable was corrected to publicly_queryable for products, templates, shops and lists. All four stay non-queryable on the frontend, which is how they always behaved.
- FIX: The page navigation of the CSV import search (“Seite 1 von 1 …”) was hard-coded German. It is now English and translatable.
- FIX: Added missing German translations for the eBay filters, the CJ catalog id and the Amazon No-API settings.
- FIX: The plugin description listed 22 Amazon marketplaces, the marketplace selection offers 17, and it promised star ratings and customer reviews, which the Amazon API does not deliver. The description now matches what the plugin does.
- FIX: Custom fields of the type “number” lost their decimals during the product refresh: everything except digits was stripped, so “1,8 l” was saved as 18. The value is now read as a number with decimal comma or point and thousands separators (requires the “Custom Fields” extension 1.0.6).
- FIX: The German translation did not load on WordPress 6.7 and later, although the language files are included. WordPress registers the text domain from the plugin header of every active plugin together with that plugin’s folder as the place to look for translations. Several extensions named the text domain of the main plugin in their header, so the extension loaded last redirected the main plugin’s translations to its own folder, where there are none. The extensions now name their own text domain (update the extensions as well).
- FIX: WordPress reported “Translation loading for the affiliate-toolkit-starter domain was triggered too early” on every request, and the name of the affiliate-toolkit widget stayed English. The widget was created while the plugin file was loaded, before the translations were available; it is now only registered on widgets_init.
- FIX: Sites running in Austrian or Swiss German or in “Deutsch (Sie)” (de_AT, de_CH, de_DE_formal) got no translation at all, because only de_DE language files are included and WordPress only looks for the exact locale. The German files are now used for every German locale, for the main plugin and all extensions.
- IMPROVED: German translation: 330 missing texts were added, most of them for extensions that now use the translations of the main plugin (Custom Fields, SiteStripe, ASA, AAWP, Field Export, Import, Import Sets, Geolocation, Product Pages, Price History, Template Pack, Amazon, eBay, Geizhals, CJ). Until now these extensions used a text domain that is never loaded and were always shown in English.
- IMPROVED: German translation reviewed: it now consistently uses the informal “du” (it mixed “du” and “Sie”), and several wrong translations were corrected – among them “No-API extension active”, which read “Keine API-Erweiterung aktiv”, a filter help text whose German version said the opposite of the setting, “Previous page” translated as “Letzte Seite”, a wrong image size and wrong plugin name in two help texts, and a number of typos and inconsistent terms.
- IMPROVED: The live search template parameters can carry the hidedisclaimer attribute of [atkp_livelist] (used by the “Frontend Search & Filter” extension 1.0.12).
- NEW: Filter atkp_product_image_alt for the alt text of product images, with the new formatter method get_image_alt( $product, $image = null ). Until now every template and image placeholder wrote the product title into the alt attribute, so an extension could only change it by rewriting the finished HTML – and that missed product boxes loaded by AJAX, search results and hover boxes. All included templates and the image placeholders now ask the filter; without a filter the alt text is still the product title. The “AI Assistant” extension 1.0.1 uses it for its AI alt texts. Own templates can use alt=”{{$formatter->get_image_alt($product)}}” (or get_image_alt($product, $image) for the images of the gallery).
- FIX: The images of the product variations had no alt attribute. They now use the title of the variation.
3.9.3
- SECURITY: Fixed a stored Cross-Site Scripting (XSS) that low-privileged users (Contributor and above) could use to run JavaScript in an administrator’s browser, reported by the Wordfence Threat Intelligence team. The product link fields were stored and printed without any escaping: the “url” cast in ATKPTools::get_casted_value() returned the submitted value verbatim (the sanitization had been commented out), and on output atkp_formatter::build_external_link() concatenated the url straight into the href attribute through a urlencode() helper that did nothing – no esc_url(), no esc_attr(). A product url containing a double quote therefore closed the href and injected arbitrary markup, for example x”>, which executed for anyone who viewed the product. Because the atkp_product post type is editable with edit_posts (capability_type “post”) and the save handler only verified its nonce, a Contributor could store such a url on a draft product, embed it anywhere with [atkp_product id=..], and the payload ran when an administrator previewed the pending post – a draft product renders on purpose. The same raw-url pattern affected the add-to-cart, customer-review and manual-offer link fields and the product image urls, which were emitted into without escaping as well. The urls are now escaped on output in every context: esc_url() for the href and for the six product image sinks, and esc_js(esc_url_raw()) for the JavaScript-link onclick variant – esc_url() alone is not enough there because its display encoding of a single quote is decoded again inside the onclick handler and would reopen the break-out. As defence in depth the “url” cast now returns esc_url_raw() so a double quote can no longer reach the stored meta value, and product_detail_save() now checks current_user_can( ‘edit_post’, $post_id ) in addition to the nonce, so the save handler enforces per-post authorization instead of accepting any product id backed by a valid nonce.
- SECURITY: Fixed an arbitrary file upload leading to Remote Code Execution by low-privileged users (Contributor and above), reported by the Wordfence Threat Intelligence team. The product image import took the file extension of the downloaded image from the url path and only replaced it when the server’s Content-Type mapped to a known WordPress image mime type. An attacker who controls the image host could answer with a Content-Type that starts with “image/” but is not a registered mime type (for example image/x-custom): the download check passed, get_extension_for_mime() returned nothing, and the extension taken from the url – “php” for http://attacker/shell.php – was kept. sanitize_file_name() does not strip a .php extension, so file_put_contents() wrote the attacker’s PHP body to wp-content/uploads, where a default server executes it. The product save handler only verified its nonce, and the atkp_product post type is editable with edit_posts, so a Contributor could read the nonce from the editor and save a draft with a prepared image url; the only non-default precondition was the administrator-set “import product image” option. The saved extension is now validated against the image extensions WordPress knows (wp_get_mime_types() filtered to image/*): when the extension derived from the url and content type is not an image extension the real type is detected from the downloaded bytes with getimagesizefromstring(), and a download that is not a genuine image is refused instead of written. In addition download_image() no longer trusts a content type merely because it begins with “image/” – a response is only accepted when its content type is a registered image mime or its bytes are a real image, so a non-image body served as image/x-custom is rejected at download time as well.
- SECURITY: Hardened the path that resolves a template name to a file (defence in depth, no exploit known). A template reference that is not a post id is resolved as a relative path below the template directories (“/.blade.php”), and the reference reaches that code from a shortcode as well as from the AJAX render endpoint, where it is taken straight from the request – for any logged-in user, and without a login whenever AJAX loading or the AJAX handler is enabled. A name containing a parent reference therefore left the template directories, and whatever the path resolved to would have been compiled and executed by BladeOne. A template name is now checked before it is used in a path (letters, digits, underscore, dash and the dot of the Blade dot notation, no directory separators, no parent references) on all four paths: the product output, the live search output, the search form output and the @include/@extends resolution inside the template engine.
- SECURITY: The “Templates” admin page was registered in the menu with the edit_pages capability, although the page itself has required manage_options since 3.9.1 – an editor saw the entry and ran into the error page. The menu entry now carries the same capability as the page.
- SECURITY: The compatibility mode for old templates read the template fields of the given id without checking that the id really belongs to a template post, which is the pattern that was fixed for the Blade render paths in 3.9.1. The old templates are filled in by placeholder replacement and are not compiled, so this was not exploitable for code execution, but the id now goes through the same guard as everywhere else (requires the “Template Compatiblity Mode” extension 1.0.5).
- FIX: The “searchtemplate not found” error of the search form printed the requested template name unescaped (requires the “Frontend Search & Filter” extension 1.0.11, and only applies when “hide error messages” is off).
3.9.2
- SECURITY: Hardened the image proxy. The key that signs the proxy addresses was built from a short letter and number pattern and, whenever the key file could not be written, fell back to a value derived from the plugin path – and it was stored as a .php file below wp-content/uploads, which servers that do not execute PHP there hand out as plain text. Anyone who knew or guessed the key could sign an arbitrary address, and the proxy fetched it and returned the response, which made it usable against hosts that are only reachable from the server. The key is now 64 random characters kept in the options table; an existing key file is moved there unchanged, so addresses already published stay valid, and the file is removed afterwards. The derived fallback is gone – without a key a signature is rejected instead of guessed. In addition every address is now checked before it is fetched (http and https only, no loopback, link-local or private targets, redirects limited), images are capped at 10 MB (ATKP_IMAGE_PROXY_MAX_BYTES), SVG is served with a sandbox Content-Security-Policy and X-Content-Type-Options: nosniff, and the last resort readfile() on the remote address – which had no timeout and no size limit – was replaced by the regular HTTP API. Unsigned requests also match the stored image addresses exactly now instead of by substring, where a single character was enough to match the first address of a product. Based on the image proxy report by x886 in the WordPress.org support forum.
- FIX: Backslashes were lost in every field saved by the plugin, which made custom templates fail with errors like “Unclosed ‘(‘ does not match ‘]'” as soon as they were saved again. Post meta has to be handed to WordPress slashed because add_post_meta() unslashes it itself, but since the coding standards pass in 3.8.6 the values already arrive unslashed from get_post_parameter(). Every save therefore stripped one level of backslashes, which is fatal for regular expressions and PHP strings inside a template body or CSS. ATKPTools::set_post_setting() now slashes before writing, and the template and shop importers do the same. Note that templates saved with an affected version have lost their backslashes in the database already and need to be corrected once. Reported by x886 in the WordPress.org support forum.
- PERFORMANCE: The shop overview took up to half a minute to load. The “Imported Product count” column ran one query per shop row, and the product table had no index on shop_id, so every one of those queries was a full table scan. The counts for all shops are now collected in a single grouped query per page load and the missing index is created. The index creation is idempotent, and the existing indexes on product_id, ean and asin were switched to the same mechanism – they used to be recreated on a table version bump and failed with “Duplicate key name”. Reported by x886 in the WordPress.org support forum.
- FIX: The discount notice fetched its data from affiliate-toolkit.com on every single admin page, before even checking whether the notice may appear on that screen. With a cold cache this blocked the page load, and because a failed request was never cached, every following page tried again and ran into the timeout once more. The screen is now checked first, failures are remembered for 15 minutes and the request uses a 5 second timeout instead of 30. The screen check also covers the plugin’s post type screens now, which it was always meant to – it compared against a post type name that cannot exist. Reported by x886 in the WordPress.org support forum.
- FIX: The delete button of a search key in the product editor was invisible. The button was rendered as an empty element and only ever got its trash icon from a stylesheet that is not loaded on the post editor screen, so the row could only be removed by guessing where to click. It now carries a dashicon plus a tooltip and an aria-label.
- SECURITY: Fixed an authenticated (administrator) SQL injection in the “Duplicate” action of the template list (CVE-2026-42721, reported by Ananda Dhakal via Patchstack). Duplicating a template copied the custom fields of the source post with one hand-built INSERT … UNION ALL SELECT statement, in which the meta key was interpolated into the query unescaped and the meta value was only passed through addslashes() instead of being prepared. The meta keys were attacker controlled because the template import took them verbatim from the keys of the uploaded JSON file, so an administrator could import a prepared template and then duplicate it to run their own SQL. The copy now goes through add_post_meta(), the import only accepts the atkp_ meta keys that the export writes, and duplicating verifies its nonce (only the delete action did) and that the source really is a template post – previously the custom fields of any post id could be copied into a new template.
- SECURITY: Fixed an information disclosure in the AJAX render endpoint. The endpoint takes the product and list ids to render straight from the request and is reachable without a login whenever AJAX loading or the AJAX handler is enabled, but it only checked the post status of products that came from a list – a product id passed directly was loaded and rendered no matter what. A visitor could therefore read the title, prices, offers and affiliate urls of a product the site owner had not published (private, pending or scheduled), and the same held for the contents of a private list. Product and list ids from the request are now resolved through the same guard that was introduced for templates: an id only resolves when it belongs to the expected post type and its status is publish or draft, which is exactly what the shortcode output (atkp_output::get_product_output) has always enforced – the AJAX path only lazy-loads that same output. The same guard was added to the “prefer local product info” branch of a list, where a product is resolved by asin through the product table: that table carries no post status, so an unpublished product could be rendered through a published list on the normal output path as well. The shop data of the list is used in that case. Reported by levanduy181.
3.9.1
- SECURITY: Fixed Remote Code Execution by low-privileged users (Contributor and above) — reported by Artus KG via WPScan. This is a complete fix for the incomplete patch of CVE-2026-6169. Template bodies are compiled and executed by the BladeOne engine, but the template renderer accepted any post id and read its atkp_template_body custom field, so a Contributor could turn their own draft post into an executable template. Template references are now resolved through a single guard that only accepts posts of the administrator-only atkp_template post type. The guard is applied to all four render paths: the AJAX render endpoint, the shortcode/product output, the live search template output, and @include/@extends targets inside the template engine.
- SECURITY: Hardened the template sanitizer as defence in depth. In addition to literal PHP tags it now also strips the Blade directives that exist purely to emit raw PHP (@php, @php … @endphp) or to instantiate an arbitrary class (@inject). Note that the sanitizer alone can never make an untrusted template safe — most of the Blade language embeds its expression into the compiled PHP — which is why the post type check above is the actual fix.
- SECURITY: The template sanitizer is now also applied on the live search template path and on @include/@extends targets, which previously bypassed it entirely.
- PERFORMANCE: Added a missing index on wp_atkp_queues_entries (post_id, id). The “Queue History” metabox in the product, list and shop editor reads the most recent queue entries for the edited post, but the table only had indexes on queue_id. On large installations MySQL had to scan the whole table backwards through the primary key for every editor page load — on a table with 1.1 million entries this single query took up to 10 seconds. With the index it is an index lookup of only the matching rows (~2 ms). Reported by a customer with database-level analysis.
- FIX: Queue table index creation is now idempotent. On a table structure version bump the existing CREATE INDEX statements were executed again and failed with MySQL error 1061 (“Duplicate key name”). Indexes are now only created when they do not exist yet, and a manually created index on post_id is detected so no redundant second index is added.
- FIX: A PHP Error (e.g. TypeError) inside a shop provider no longer stops the cronjob permanently. The queue processing only caught Exception, so a PHP Error escaped both the inner and the outer handler and killed the run before the entry statuses were written. The same batch of 10 entries was then fetched again on every following cron run, the queue stayed “active” forever and — because queue cleanup only runs after a queue completes — old queues were never deleted again. All cronjob handlers now catch Throwable and mark the affected entries as errors so the queue can continue.
- FIX: Endless loop in the queue processing when an atkp_queue_process_entries_* filter returns only part of the entries it was given. The dropped entries kept the status “prepared” and were delivered again by get_next_entries on every iteration. They are now marked as not processed, like entries the filter leaves untouched.
- FIX: The “Delete” row action in the queue and template lists always failed with “Go get a life script kiddies”. The link was created with the nonce action atkp_edit_queue/atkp_edit_template but verified against atkp_delete_link.
- IMPROVED: The active queue is now selected deterministically (oldest first) instead of relying on the storage order of the table.
- NEW: Stalled queues are detected and aborted. A queue that makes no progress across several cron runs — because the same package always dies on a fatal error, a timeout or out of memory — used to stay “active” forever, which blocked every new queue and stopped the cleanup of old queues. The number of open entries is now tracked per run (in internalstatus); if it does not change for 3 consecutive runs and no entry has been written for 30 minutes, the queue is set to “abort”, the remaining entries are marked as errors and the next cron run starts a fresh queue. Both thresholds are filterable via atkp_queue_stall_minutes and atkp_queue_max_stall_retries, and the new action atkp_queue_aborted fires on abort.
- IMPROVED: Old queues are now cleaned up on every cron run instead of only after a queue has completed, so a single stalled queue can no longer stop the cleanup permanently. Active queues are excluded from the cleanup so the queue currently being processed is never deleted.
- PERFORMANCE: Added an index on wp_atkp_queues_entries (queue_id, updatedon). The cronjob reads the last entry activity of the running queue on every run, which previously sorted all entries of that queue (on large installations hundreds of thousands of rows) instead of doing an index lookup.
- IMPROVED: The “Retries” column of the queue list now shows the number of cron runs without progress. The counter is reset as soon as the queue advances, so it no longer grows with the plain number of runs.
- FIX: The disclaimer with the “Last updated on …” line was missing in all templates — most visibly in the WooCommerce price comparison tab, where it is the only place the update time is shown. The option cache introduced in 3.8 carries its own table of fallback values, and because that table pre-seeds every key, isset() always matched and the real defaults in atkp_options were never reached. show_disclaimer therefore resolved to 0 and disclaimer_text to an empty string on every installation that had …






