Safeguard
Vulnerability Analysis•

CVE-2023-29051: High Access Control Bypass in OX App Suite Templates

CVE-2023-29051 lets user-defined OXMF templates reach part of the OX App Suite Java API. Update to 7.10.6-rev52 or 8.18 per the vendor advisory.

Safeguard Security Team
3 min read

CVE-2023-29051 is an access control flaw in Open-Xchange OX App Suite. User-defined OXMF templates could reach part of the internal Java API, because the switch that disables them by default did not work. NVD and the vendor score it 8.1, High. Fixed in 7.10.6-rev52 and 8.18.

What's affected

Open-Xchange advisory oxas-adv-2023-0006 lists OX App Suite backend 7.10.6-rev51 and 8.17 as the last affected versions. Fixed versions are 7.10.6-rev52 and 8.18, with patch release 6251.

Source conflict on versions: the NVD product list covers only the 7.10.6 line, while the vendor also lists 8.x. Use the vendor's versions.

Severity agrees: 8.1, High, vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N. The vendor says no publicly available exploits are known and plans to remove the feature in future generations of the product.

How to check if you're exposed

Check your installed version. On Debian or Ubuntu run dpkg -l open-xchange-core, and on RPM based systems run rpm -q open-xchange-core. The package version shows the product line and revision, for example 7.10.6 followed by a revision number. Compare it with the fixed revision above, and repeat on every backend node in the cluster.

If you use a managed or hosted OX App Suite service, ask your provider which revision it runs.

The vendor says the existing switch to disable user-generated templates did not work in this case, so do not treat your configuration as proof that you are safe.

What to do now

  1. Update the backend to 7.10.6-rev52 or 8.18, or later, on every node. Patch release 6251 is the reference.
  2. Do not rely on the old switch for user-generated templates as a mitigation. The advisory says it was not effective.
  3. Apply earlier revisions too if you are behind, since this fix builds on rev51 and 8.17.
  4. Review who can create templates in your deployment.
  5. Check the Gold page for this CVE for later changes.

Why it matters

The record classes the flaw as CWE-284 (Improper Access Control). A feature that is meant to be off by default was reachable anyway, and templates written by users could touch a limited part of the internal Java API. The vendor says this could let unauthorised users discover and modify application state, including objects belonging to other users and contexts.

The cross-user effect is what raises the score. In a multi-tenant mail platform, one account reaching another account's objects breaks the main boundary the product depends on. The vendor response is two-part: make the default switch work as intended, and retire the feature later.

Disabled-by-default features are a known source of surprises. A flag that is supposed to turn something off needs a test that proves it does. When you review your own software, check that every off switch has a test, and read vendor notes for any statement that a switch did not take effect.

Quick check

Why not just keep the feature switched off?

The vendor says the switch did not work in this case. The fix makes it work, and you need the fix to rely on it.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.