Magento LTS's guest order "protect code" can be brute-forced too easily

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2023-41879: 1.25% estimated exploitation activity in the next 30 days; percentile 69.47 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Guest orders may be viewed without authentication using a "guest-view" cookie which contains the order's "protectcode". This code is 6 hexadecimal characters which is arguably not enough to prevent a brute-force attack. Exposing each order would require a separate brute force attack. Patches None. Workarounds Implementing rate-limiting at the web server would help mitigate the issue. In particular, a very strict rate limit (e.g. 1 per minute per IP) for the specific route (sales/guest/view/) would effectively mitigate the issue. References Email from Frank Rochlitzer (f.rochlitzer@b3-it.de) to security@openmage.org: Summary The German Federal Office for Information Security (BSI) found the following flaw in OpenMage through a commissioned pen test: The web application was found to accept certain requests even without prior strong authentication if the person making the request has data that is non-public but also not secret, such as easily easily guessed transaction numbers or…

Published by the source

11 Sep 2023, 20:45 UTC

Last modified by the source

11 Nov 2023, 05:04 UTC

Source last checked

26 Oct 2026, 14:11 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-9358-cpvx-c2qp

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-41879

Advisory: Magento LTS's guest order "protect code" can be brute-forced too easily
IDs: CVE-2023-41879, GHSA-9358-cpvx-c2qp
Record: https://patchnext.com/advisories/cve-2023-41879 (revision 1, source checked 26 Oct 2026, 14:11 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: openmage/magento-lts 20.1.1, 19.5.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist openmage/magento-lts: affected <= 19.5.0; >= 20.0.0, <= 20.1.0; fixed in 20.1.1, 19.5.1

## Suggested inspection (read-only)
- Packagist openmage/magento-lts: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on openmage/magento-lts.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-9358-cpvx-c2qp (GitHub-reviewed advisory GHSA-9358-cpvx-c2qp lists affected ranges: Packagist openmage/magento-lts >=0 =20.0.0 <=20.1.0)

Commands are suggestions: review each one before running it.