FKIE_CVE-2026-56828

Vulnerability from fkie_nvd - Published: 2026-10-28 16:17 - Updated: 2026-11-04 23:10
Summary
Shopper is a Headless e-commerce Admin Panel. From 2.8.0 until 2.8.1, three Shopper Livewire admin components retain authorization gaps after the earlier team-settings authorization fix. A staff member with only `view_users` and `access_dashboard` can mutate permissions, create an administrator, or delete roles. In `packages/admin/src/Livewire/Components/Settings/Team/Permissions.php`, `togglePermission` and `removePermission` authorize `view_users` rather than the stronger `access_setting` permission; `packages/admin/resources/views/livewire/components/settings/team/permissions.blade.php` exposes permission IDs in `wire:click` handlers. The attacker can grant arbitrary permissions to the bound role, including `access_setting` on the attacker's own role, or delete permission definitions. In `packages/admin/src/Livewire/SlideOvers/CreateTeamMember.php`, `mount()` and `store()` also accept `view_users`, and the client-selected `role_id` can identify the admin role, allowing creation of a pre-verified administrator with an attacker-chosen password. In `packages/admin/src/Livewire/Pages/Settings/Team/RolePermission.php`, `deleteAction` has no action authorization and is only conditioned on `can_be_removed`, while page access requires `view_users`. Deleting a removable role removes access for assigned users, enabling RBAC denial of service as well as privilege escalation. This issue is fixed in version 2.8.1.
Impacted products
Vendor Product Version

{
  "affected": [
    {
      "affectedData": [
        {
          "product": "shopper",
          "vendor": "shopperlabs",
          "versions": [
            {
              "status": "affected",
              "version": "\u003e= 2.8.0, \u003c 2.8.1"
            }
          ]
        }
      ],
      "source": "security-advisories@github.com"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "Shopper is a Headless e-commerce Admin Panel. From 2.8.0 until 2.8.1, three Shopper Livewire admin components retain authorization gaps after the earlier team-settings authorization fix. A staff member with only `view_users` and `access_dashboard` can mutate permissions, create an administrator, or delete roles. In `packages/admin/src/Livewire/Components/Settings/Team/Permissions.php`, `togglePermission` and `removePermission` authorize `view_users` rather than the stronger `access_setting` permission; `packages/admin/resources/views/livewire/components/settings/team/permissions.blade.php` exposes permission IDs in `wire:click` handlers. The attacker can grant arbitrary permissions to the bound role, including `access_setting` on the attacker\u0027s own role, or delete permission definitions. In `packages/admin/src/Livewire/SlideOvers/CreateTeamMember.php`, `mount()` and `store()` also accept `view_users`, and the client-selected `role_id` can identify the admin role, allowing creation of a pre-verified administrator with an attacker-chosen password. In `packages/admin/src/Livewire/Pages/Settings/Team/RolePermission.php`, `deleteAction` has no action authorization and is only conditioned on `can_be_removed`, while page access requires `view_users`. Deleting a removable role removes access for assigned users, enabling RBAC denial of service as well as privilege escalation. This issue is fixed in version 2.8.1."
    },
    {
      "lang": "es",
      "value": "Shopper es un Panel de Administraci\u00f3n de comercio electr\u00f3nico Headless. Desde la versi\u00f3n 2.8.0 hasta la 2.8.1 incluida, tres componentes de administraci\u00f3n de Shopper Livewire conservan lagunas de autorizaci\u00f3n despu\u00e9s de la correcci\u00f3n de autorizaci\u00f3n de configuraci\u00f3n de equipo anterior. Un miembro del personal con solo \u2019view_users\u2019 y \u2019access_dashboard\u2019 puede modificar permisos, crear un administrador o eliminar roles. En \u2019packages/admin/src/Livewire/Components/Settings/Team/Permissions.php\u2019, \u2019togglePermission\u2019 y \u2019removePermission\u2019 autorizan \u2019view_users\u2019 en lugar del permiso m\u00e1s fuerte \u2019access_setting\u2019; \u2019packages/admin/resources/views/livewire/components/settings/team/permissions.blade.php\u2019 expone los ID de permiso en los manejadores \u2019wire:click\u2019. El atacante puede otorgar permisos arbitrarios al rol vinculado, incluyendo \u2019access_setting\u2019 en el propio rol del atacante, o eliminar definiciones de permisos. En \u2019packages/admin/src/Livewire/SlideOvers/CreateTeamMember.php\u2019, \u2019mount()\u2019 y \u2019store()\u2019 tambi\u00e9n aceptan \u2019view_users\u2019, y el \u2019role_id\u2019 seleccionado por el cliente puede identificar el rol de administrador, permitiendo la creaci\u00f3n de un administrador preverificado con una contrase\u00f1a elegida por el atacante. En \u2019packages/admin/src/Livewire/Pages/Settings/Team/RolePermission.php\u2019, \u2019deleteAction\u2019 no tiene autorizaci\u00f3n de acci\u00f3n y solo est\u00e1 condicionado por \u2019can_be_removed\u2019, mientras que el acceso a la p\u00e1gina requiere \u2019view_users\u2019. Eliminar un rol removible elimina el acceso para los usuarios asignados, lo que permite la denegaci\u00f3n de servicio RBAC, as\u00ed como la escalada de privilegios. Este problema se ha solucionado en la versi\u00f3n 2.8.1."
    }
  ],
  "id": "CVE-2026-56828",
  "lastModified": "2026-11-04T23:10:00.223",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "HIGH",
          "baseScore": 8.8,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "privilegesRequired": "LOW",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
          "version": "3.1"
        },
        "exploitabilityScore": 2.8,
        "impactScore": 5.9,
        "source": "security-advisories@github.com",
        "type": "Secondary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2026-56828",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "total"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2026-11-03T13:06:00.958748Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2026-10-28T16:17:08.220",
  "references": [
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/shopperlabs/shopper/commit/ac9a76044a8e4a2b570b438d66cf3007f3dc479e"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/shopperlabs/shopper/compare/v2.8.1...v2.9.2"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/shopperlabs/shopper/pull/514"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/shopperlabs/shopper/releases/tag/v2.8.1"
    },
    {
      "source": "security-advisories@github.com",
      "url": "https://github.com/shopperlabs/shopper/security/advisories/GHSA-j328-xmgp-j4q3"
    }
  ],
  "sourceIdentifier": "security-advisories@github.com",
  "vulnStatus": "Deferred",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-285"
        },
        {
          "lang": "en",
          "value": "CWE-862"
        }
      ],
      "source": "security-advisories@github.com",
      "type": "Secondary"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.