CVE-2026-81828 · Package
NO FIX YET · SEE WHAT TO DO
An authenticated back-office user with catalog permission can set a product-store survey template location to an arbitrary URL, and the server fetches it and renders the content into pages shown to shoppers. An attacker can read internal network, cloud-metadata and local files through file:// URLs.
first public Nov 5, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams running Apache OFBiz 24.09 before 24.09.08 with product-store surveys in use. The exposure needs an authenticated back-office user with catalog permission, so teams that restrict that permission narrowly are at lower risk but should still upgrade.
Not affected if no-catalog-permission-users, not-on-24.09, patched-24.09.08
Who cares apache-ofbiz, java, self-hosted
24.09.x before 24.09.08 is affected.24.09.08.Server-Side Request Forgery in SurveyWrapper in Apache OFBiz 24.09 before 24.09.08 on all platforms allows an authenticated back-office user holding catalog permission to cause the server to fetch and render attacker-controlled URLs — including internal network and cloud-metadata endpoints and local files via file:// — by setting an arbitrary URL as a product-store survey's template location, causing SurveyWrapper.getTemplate to call URL.openStream() on the resolved location and compile the fetched content as a FreeMarker template with no scheme or host validation, unlike the sibling widget location-loaders (ScreenFactory, FormFactory, GridFactory, MenuFactory, TreeFactory, ThemeFactory) which validate the resolved location before loading it. The fetched content is rendered into the HTTP response of any shopper who subsequently loads the affected product-store survey, making the disclosure non-blind. Users are recommended to upgrade to version 24.09.08, which fixes this issue.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.