Critical Adobe Commerce Flaw CVE-2025-54236 Alert

After the fix, exported products filtered by a Yes/No attribute contain the expected products that respect the applied filters. Now, after the fix, if you mark the product swatch image column with the configured empty marker, the image will be set to hidden. Name field is now required when creating new products through the import process (admin or API). This aligns with the expected input from the export controller and prevents static analysis warnings. Previously, this “types” field did not exist in the MediaGallery GraphQL request.

Adobe Commerce is no long make many requests to FedEx API service for the access token. Now, full-text search returns matching products if the minimum should match condition is met across all searchable fields collectively, rather than requiring the condition to be satisfied by a single field. Fixed an issue where error messages were not immediately shown for invalid GET requests. Fixed an issue where DynamicStorage did not filter by entity_type, causing CMS pages to be incorrectly treated as products in category URLs; malformed URLs now correctly return a 404 instead of serving CMS content. After the fix catalog price rules now apply correctly when special_price is set at website level by checking the website’s default store first. Before the fix catalog price rules did not apply when special_price was set only at website level (not at “All Store Views”).

Adobe Commerce Catalog Product List widget now returns the correct total count and pagination (e.g. 9 items across pages as configured). Fixed issue where only three products were displayed per row on category pages.Now, four products are displayed per row as expected. Fixed issue where switching store views from the storefront header did not work until cache was manually cleared.Now, store view switching works correctly without requiring a cache clean. Now, the special price is shown properly along with the regular price, ensuring consistent pricing display across product types. Added the missing indexing of required columns in catalog_product_entity_int table

After the fix, when minification is enabled there https://best-adobe-commerce-implementation-partners.com/ are no non-minified JS resources requested. Prior to the fix, even if you had minification enabled some of the JS files were requested without the “min” prefix resulting in 404 status code. Changelog tables cleanup is now running in batches to avoid heavy delete operations. Incorrect AWS S3 credentials no longer causes pages to load infinitely on storefront. Previously, an irrelevant variable name, $defaultCountry, was used in the search engine module, causing confusion. Updated the README Leaders link by replacing the permanently redirected and expired URL with correct working links, ensuring contributors and maintainers pages open properly.

Fixed an issue where creating an order in the backoffice with multiple products, including one with custom options, unintentionally added extra products and caused errors. The system now send a shipment confirmation email as it is enabled in the store configuration where the order was placed. Fixed issue where the order_date field in GraphQL response returned in yyyy-mm-dd format.Now, the order_date is displayed correctly in dd-mm-yyyy format. The system is working as expected and after reorder from the backend the order number will be unique 8 digits

Previously, only the first 20 values or another selected page values were displayed, causing the remaining values to be missing. Prior to the fix, the logout action was not being completed properly on the cart page, if the logged in user company was no longer enabled. Fixed issue where cart price rules with the “Price in Cart less than” condition were incorrectly applied to ineligible products.Now, coupons are properly validated and rejected when cart item prices do not meet the configured rule conditions. Adobe Commerce now allows guest shoppers to successfully place orders when the middle name field is configured as required in the Admin. Fixes the issue where the daily aggregated orders report takes an excessive amount of time to generate for a large volume of orders, causing disk I/O spikes and performance degradation.

This PR reduces the extra query call using count() if the product collection is already loaded when calling Product Graphql with media_gallery field included in it. Ensured correct storefront price display and “As low as” label behavior for products under Category C. Updated the failing test to align with actual pricing behavior for configurable products when all child products have the same price.The assertion now correctly validates the displayed price, preventing false test failures without impacting functionality. Card information is now properly persisted and displayed when using saved cards with the Sales payment action, matching the behavior when using the Authorization payment action for PayflowPro. Prior to the fix, when ordering a bundle product with “Ship together” option enabled, the order status did not automatically switch to “complete” after invoice and shipment.

Admin product form save/edit is faster for large attribute sets by reducing expensive client-side validation passes while preserving existing validation behavior. The Admin export grid and download action now expose only completed export files whose format matches the configured Export File Format options, preventing partial downloads and excluding unrelated files from the UI. Improved Media Gallery performance by changing directory tree loading to on-demand node expansion instead of building the full tree upfront, significantly reducing initial gettree response time on large media directory structures Fixed the JavaScript warning that appeared in the browser console when Charts were enabled for the admin dashboard. After the fix, both can be saved successfully even when multiple attribute options are still present. Improved file upload for custom ui component with multiple select to allow upload on upload area click.


Comments

Leave a Reply

Your email address will not be published. Required fields are marked *