Skip to content

26.11.2

Choose a tag to compare

@fballiano fballiano released this 19 Nov 13:22
· 22 commits to 26.11 since this release
Immutable release. Only release title and notes can be modified.
f82bc70

Warning

This release has no package and no SBOM. Use 26.11.3, which has the same code.

Maho 26.11.2 is a maintenance release for the 26.11 line: no new features, just fixes backported from main. It brings the security fixes of OpenMage 20.19.1 (admin permissions, layout updates, widgets, legacy API secrets and escaping), and closes the same order permission gap in the Maho API, so upgrade soon.

Creating Maho is a massive effort that requires all the help possible, please join our sponsorship program.
It will make all the difference in the world!
become a sponsor

Maho rocks! 🚀
https://mahocommerce.com
https://demo.mahocommerce.com


⚠️ Upgrade notes

  • Admin roles: creating, capturing, voiding or canceling an invoice, a shipment or a credit memo now needs the matching permission under Sales > Orders > Actions, in addition to the grid permission. Global Search needs Catalog > Manage Products, Customers > Manage Customers and Sales > Orders > Actions > View. A role with only the order Edit permission cannot reorder. Check your custom roles after the upgrade.
  • Admin sessions: an admin who loses all roles is signed out on the next admin page, and /api/admin/* refuses the session. An admin cannot change their own role, on System > Permissions > Users or on System > Permissions > Roles: another administrator must make that change.
  • API with an admin token: the order and document actions need the same Sales > Orders > Actions permissions as the admin panel. Placing an order, also from a guest cart, needs Create. On /api/graphql, each operation now needs the admin ACL of its resource, as on REST. An integration that uses an admin token with a limited role can get a 403 where it did not before.
  • Grid column callbacks: a frame_callback, filter_condition_callback or getter runs only when it is a closure, an invokable object or an [object, method] array. An extension that gives a "Class::method" string must change it.
  • Custom layout updates that contain admin blocks are refused on save, and a CMS page ignores a stored update that the validator refuses.
  • Widget instances: the upgrade removes the layout updates of widget instances whose type no enabled module declares, or whose XML has an unexpected shape. Each removal is in var/log/widget_instance_cleanup.log. Enable the module that gives the widget type before the upgrade, or save the widget instance again after it.
  • Legacy API: customer reads return confirmation as a boolean and no longer return twofa_secret, and a filter on password_hash, rp_token, twofa_secret or confirmation is refused. Cart and order reads no longer return card data.
  • Custom variables: a code must start with a letter and contain only letters, digits, underscores, hyphens and slashes. An existing code that does not change still saves.

🔒 Security

  • Fixed the security issues that OpenMage 20.19.1 fixed: admin permissions, layout updates, widgets, legacy API secrets and escaping:
    • An admin with the permission for a document grid could create, capture, void or cancel invoices, shipments and credit memos without the matching order action permission. An admin with only the order Edit permission could reorder, or move the edited order to another customer or store.
    • After a role change, other sessions of the same admin kept the old permissions, and an admin removed from the role stayed signed in.
    • A custom layout update could put admin blocks on the storefront, and a grid column could call a static method. An admin could save a widget instance with any type, which went into the storefront layout without escaping.
    • {{config path="..."}} could read an encrypted value through an attribute selector in the path.
    • The legacy SOAP, XML-RPC and REST v1 APIs returned password hashes, reset tokens, the confirmation key and card data.
    • Tracking details, configurable option labels and downloadable link titles showed without escaping.
    • The same order permission gap was in the Maho API: with an admin token, the REST, GraphQL and MCP order and document actions checked only the grid permission, and /api/graphql did not check the admin ACL of the resource at all.

🐛 Fixes

Full changelog: 26.11.1...26.11.2