github OpenMage/magento-lts v20.18.3
v20.18.3 🌈

36 minutes ago

Security

This release fixes 12 security issues: 6 are published with CVE identifiers and 6 as GitHub Security Advisories only. Upgrade as soon as possible. v20.18.3 is a security-only patch release on top of v20.18.2 and fixes all twelve. The same fixes ship in v20.19.1 and, for the 21.x pre-release line, in v21.0.0-beta4.

Scores are CVSS 3.1. Several of these issues let an administrator whose role is limited to one area (catalog, CMS, widgets, email templates) reach data or code execution that the role is meant to keep out of reach. If you give restricted admin roles to people you would not trust with full access, upgrade first.

Advisories with a CVE

Advisory Issue Severity CVE Fixed in
GHSA-pqgf-g7m7-vh98 Stored XSS in the admin order view via an unescaped guest checkout email address Critical 9.3 requested 20.18.3, 20.19.1
GHSA-5fmm-3f76-87r8 Path traversal in downloadable product and media gallery file names lets a catalog-only admin rename arbitrary files High 7.2 requested 20.18.3, 20.19.1
GHSA-8m3h-7cgh-jf96 Admin grid blocks in custom layout updates let a catalog- or CMS-only admin run code through a column callback High 7.2 requested 20.18.3, 20.19.1
GHSA-v7cc-v57g-wx93 Unvalidated widget instance type lets a Widgets-only admin role inject layout XML and execute code Medium 6.8 (7.2 with the layout cache disabled) requested 20.18.3, 20.19.1
GHSA-c686-fw3h-35cq SOAP/XML-RPC customer, cart and order APIs return reset tokens, confirmation keys and stored payment secrets to read-only roles Medium 6.5 requested 20.18.3, 20.19.1
GHSA-g8fq-xm46-qcpx Attribute-selector config paths bypass the email template getConfig guard and disclose encrypted secrets Medium 4.9 requested 20.18.3, 20.19.1

Advisories without a CVE

These are published so you can track them. Each one either needs an administrator account and crosses no authority boundary, or has low impact.

Advisory Issue Severity Fixed in
GHSA-g5qf-m762-993x Stored XSS in admin order views via shipment tracking details and configurable option labels Medium 6.1 20.18.3, 20.19.1
GHSA-qrpm-g4h5-qrgr Stored XSS in the admin "Insert Variable..." dialog via custom variable codes and email template variable labels Medium 6.1 20.18.3, 20.19.1
GHSA-fwmh-c5gm-2pqm Admin panel sessions survive user deactivation and role changes Medium 5.9 20.18.3, 20.19.1
GHSA-5xfj-mgf7-27gm Cross-site requests can place customer orders through PayPal Express actions Medium 4.3 20.18.3, 20.19.1
GHSA-788v-r8j7-99g3 Insufficient granular ACL enforcement in admin order, search and Dataflow controllers (follow-up) Low 3.8 20.18.3, 20.19.1
GHSA-jf5h-w7h5-j7jj Stored XSS via unescaped child product name in the storefront "Only X left" details table Low 3.5 20.18.3, 20.19.1

Behaviour changes and upgrade notes

Review these before you upgrade. Most need no action unless you run an integration that reads secrets through the API, an extension that saves widgets or grid callbacks in unusual ways, or restricted admin roles.

Database upgrades

  • Widget layout cleanup (Mage_Widget 1.6.0.2). The upgrade removes the generated layout updates of widget instances whose type no enabled module declares, and of any widget layout update whose stored XML is not exactly what the generator produces. The widget instances are kept; saving one again regenerates its layout. Review var/log/widget_instance_cleanup.log after upgrading. If an extension was disabled during the upgrade, re-enable it and save its widget instances again.
  • Admin ACL version (Mage_Admin 1.6.1.6). admin_user.reload_acl_flag becomes a per-user version number. Extensions that set it to 1 to force a reload keep working.

APIs

  • SOAP/XML-RPC customer.info, customer.list and cart.info no longer return password_hash, the password-reset token fields or the raw confirmation key (confirmation is a boolean). cart.info and sales_order.info no longer return encrypted card data (cc_number_enc, cc_cid_enc), card debug fields or PayPal secure tokens. Filters on those attributes are refused. REST customer reads follow the same rules. Integrations that copied password hashes or decrypted card numbers through the API must stop relying on it.

Admin roles

  • Admin users who are deactivated or lose their role are logged out of every open session on their next request, and role changes reach every open session. Administrators can no longer change their own active status or role.
  • Creating invoices, shipments and credit memos needs the matching Sales › Orders › Actions permission (plus Capture / Cancel for those invoice actions). Edit-only roles can no longer create orders through the edit screen. Global Search only shows products, customers and orders to roles that can see them. Dataflow GUI profile roles can no longer reach Advanced Profiles or post raw actions XML.

Layout updates and widgets

  • Custom layout updates (products, categories, CMS pages) that declare an admin block or use the json attribute are refused on save. CMS page layout updates are validated again when the page renders, and a stored update that fails is not applied, so pages that carry an old, now-invalid update render without it.
  • Widget instances must use a widget type declared in a widget.xml; page groups with unknown options or special characters in the block reference or template are refused.
  • Grid column frame_callback and getter options given as a static ["Class", "method"] array are no longer called. Use a closure or an [object, "method"] callable.

Templates and content

  • getConfig() in email and newsletter templates returns nothing for paths that are not plain section/group/field paths (for example with @, = or quotes).
  • Saving a custom variable rejects a code that does not start with a letter or contains characters other than letters, digits, _, - and / (the rule the admin form has always applied). The Insert Variable... dialog shows labels as text and no longer runs scripts in its content.
  • Downloadable sample and link file names and new media gallery image names with a .. path segment, a NUL byte or no name are refused on product save, including stored names.
  • PayPal Express: Place Order needs a POST with the form key, the shipping method update needs the form key, and the return URL needs a matching token. The stock templates and review.js already send them; custom code that hard-codes these URLs must add the form key.
  • Configurable option labels that deliberately contain HTML now show as text in admin order, invoice, shipment and credit memo item lists and in the admin customer cart and wishlist grids.
  • Template overrides. If your theme overrides any of these templates, apply the same escaping: sales/order/view/info.phtml, sales/order/view/tab/info.phtml, sales/order/view/tracking.phtml, sales/items/renderer/default.phtml and the downloadable and bundle sales item renderers (admin); cataloginventory/stockqty/composite.phtml (base and rwd), sales/order/trackinginfo.phtml and shipping/tracking/popup.phtml (storefront).
  • JavaScript cache. js/mage/adminhtml/variables.js changed. Flush the JavaScript/CSS cache (and any CDN copy) after upgrading so admin browsers load the new file.

If restricted admins have held System › Transactional Emails or Newsletter Templates, or product, CMS or widget editing, consider rotating payment and carrier credentials and checking app/etc/local.xml access.

Thanks

We thank every researcher who reported these issues through GitHub and HackerOne. Each advisory names its reporters.

Changes

Security fixes only, on top of v20.18.2. The new unit tests are adapted to PHPUnit 9.

Full Changelog: v20.18.2...v20.18.3

Don't miss a new magento-lts release

NewReleases is sending notifications on new releases.