Vai al contenuto

Maho 26.11.2 brings the OpenMage 20.19.1 fixes and closes the order permission gap in the API

The security fixes of OpenMage 20.19.1 land in the 26.11 line, with the same order permission gap closed in the Maho API, and the PayPal button comes back on the pages the browser restores.

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

The release was published without its package and without its SBOM. The code is the same as 26.11.3, which is the version to install, and the article on 26.11.3 covers what changes.

Security

#1872 gathers the fixes. On permissions, 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, and an admin with only the order Edit permission could reorder, or move the edited order to another customer or store. After a role change, the other sessions of the same admin kept the old permissions, and an admin removed from the role stayed signed in.

On content, a custom layout update could put admin blocks on the storefront, a grid column could call a static method, and 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 on /api/graphql the admin ACL of the resource was not checked at all.

Roles, sessions and API

  • Roles: creating, capturing, voiding or cancelling 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, and 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 makes 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, and on /api/graphql each operation 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.

Before you update

The patch adds no settings. These are the points to plan for.

  • 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 passes a "Class::method" string has to 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 provides the widget type before the upgrade, or save the widget instance again after it.
  • Legacy API: a customer read returns confirmation as a boolean and no longer returns 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.

The other fix

#1863 brings the PayPal button back on a storefront page that the browser restores after the session ended, which happens often on iOS Safari: the button, the card fields and the Pay Later message were missing. They now load, and a PayPal click that fails on a page that is too old asks the shopper to refresh the page.

Text prepared with the help of AI and checked against the source before publication. It can still contain mistakes: if you find one, report it.Read the manifesto

Source: Release 26.11.2

Does your store still sell?

Tell us where you are starting from: we reply with a first assessment, no strings attached.

Ask for the store assessment