LiveActive security incident?Get immediate response
CVE Record

CVE-2026-28225: Manyfold has IDOR in ModelFilesController

Manyfold is an open source, self-hosted web application for managing a collection of 3d models, particularly focused on 3d printing. Prior to version 0.133.1, the `get_model` method in `ModelFilesController` (line 158-160) loads models using `Model.find_param(params[:model_id])` without `policy_scope()`, bypassing Pundit authorization. All other controllers correctly use `policy_scope(Model).find_param()` (e.g., `ModelsController` line 263). Version 0.133.1 fixes the issue.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2026-28225 affects Manyfold, a self-hosted 3D model management application. Before version 0.133.1, one controller could load model records without the normal authorization scope. This may let a user affect model file actions they should not be allowed to access. Public sources rate it medium severity and identify version 0.133.1 as the fix.

Executive priority

Treat as a near-term update for organizations using Manyfold, especially shared or internet-accessible instances. It is not currently supported as actively exploited by the provided sources, but authorization bypasses can undermine data governance and tenant separation.

Technical view

Manyfold’s ModelFilesController get_model method used Model.find_param(params[:model_id]) instead of policy_scope(Model).find_param(), bypassing Pundit authorization scoping. The issue is classified as CWE-639, authorization bypass through user-controlled key. CVSS 3.1 is 5.3, network exploitable, low complexity, no privileges or user interaction, with low integrity impact.

Likely exposure

Exposure is limited to Manyfold deployments running versions earlier than 0.133.1. The cited advisory describes a self-hosted web application, so internet-facing or broadly accessible instances have higher operational risk. The provided sources do not identify other affected products or hosted services.

Exploitation context

The CVE record does not indicate CISA KEV listing, and the provided sources do not report active exploitation. The flaw is authorization-related and network reachable per CVSS, but public evidence here does not establish real-world abuse or exploit tooling.

Researcher notes

The root cause is missing Pundit policy_scope in ModelFilesController while other controllers reportedly use scoped lookup. The source bundle names lines 158-160 and compares ModelsController line 263, but this analysis relies on the advisory description rather than independent code review.

Mitigation direction

  • Upgrade Manyfold to version 0.133.1 or later.
  • Review the GitHub security advisory for vendor guidance.
  • Restrict access to Manyfold until upgraded, especially for untrusted users.
  • Review model and file permissions after remediation.

Validation and detection

  • Inventory Manyfold instances and confirm running versions.
  • Flag any Manyfold version earlier than 0.133.1.
  • Confirm upgrade completion to 0.133.1 or later.
  • Review application logs for unusual model file access attempts.
  • Validate that user access boundaries still match business expectations.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-639: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-28225 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2026-28225Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
manyfold3dmanyfold< 0.133.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-639 · source CWE mapping

Authorization Bypass Through User-Controlled Key

Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.