Approved changes feed: RSS · Atom
cpe:2.3:a:strapi:strapi:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Strapi (6538852c-3d36-5907-9ffe-d46d2af65fd8) |
|---|---|
| Product | Strapi (9e85d541-fc66-5178-86c6-60251f5c990b) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from purl2cpe mapping
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:docker/strapi/strapi |
purl2cpe | 2026-06-01 10:15:44.776196 |
pkg:github/strapi/strapi |
purl2cpe | 2026-06-01 10:15:44.776200 |
pkg:npm/strapi |
purl2cpe | 2026-06-01 10:15:44.776204 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-108114 |
vulnerable | 2026-11-03 10:18:01.643117 |
Strapi 5.47.0 through 5.57.0 Improper Authorization via Admin API Token Field Permissions
MEDIUM (4.3)
Strapi 5.47.0 through 5.57.0 contains an improper authorization vulnerability that allows admin API tokens to retain all-field Content Manager access after the owner's role is field-restricted. Because reconcileTokenPermissionsToUserCeiling ignores token permissions with omitted or null fields, token holders can keep reading content fields an administrator removed from the role.
Published: 2026-10-10T14:15:50.908Z
Updated: 2026-10-14T02:18:14.320Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-90561 |
vulnerable | 2026-09-16 04:33:05.612043 |
Strapi 4.x through 4.26.2 and 5.x before 5.48.1 Stored XSS via WYSIWYG
HIGH (8.7)
Strapi versions 4.x through 4.26.2 and 5.x before 5.48.1 contain a stored cross-site scripting vulnerability in the content manager WYSIWYG preview component that fails to strip script tags from rich text. An Author-role user can store malicious script tags in rich text fields that execute in an Editor or Super Admin's session when the preview pane is expanded, enabling account takeover.
Published: 2026-09-13T10:45:35.988Z
Updated: 2026-09-24T14:21:46.210Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-57997 |
vulnerable | 2026-07-29 01:03:16.568237 |
Strapi users-permissions - JWT Algorithm Confusion via Missing Algorithm Configuration
MEDIUM (4.8)
Strapi users-permissions plugin fails to restrict JWT algorithms when plugin::users-permissions.jwt.algorithm is not explicitly configured, allowing acceptance of HS384 and HS512 tokens alongside HS256. Attackers possessing the jwtSecret can mint tokens with non-standard HMAC variants to bypass algorithm restrictions and weaken authentication controls.
Published: 2026-06-29T21:16:35.174Z
Updated: 2026-11-08T14:06:43.253Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-27886 |
vulnerable | 2026-06-08 07:55:14.081826 |
Strapi may leak sensitive data via relational filtering due to lack of query sanitization
Strapi is an open source headless content management system. Strapi versions starting in 4.0.0 and prior to 5.37.0 did not sufficiently sanitize query parameters when filtering content via relational fields. An unauthenticated attacker could use the `where` query parameter on any publicly-accessible content-type with an `updatedBy` (or other admin-relation) field to perform a boolean-oracle attack against private fields on the joined `admin_users` table, including the `resetPasswordToken` field. Extracting an admin reset token via this oracle made full administrative account takeover possible without authentication. When a filter such as `where[updatedBy][resetPasswordToken][$startsWith]=a` was applied to a public Content API endpoint, the underlying query generation performed a `LEFT JOIN` against the `admin_users` table and emitted a `WHERE` clause referencing the joined column. The query parameter sanitization layer did not block operator chains that traversed into relational target schemas the caller had no read permission on, allowing the response count to be used as a one-bit oracle on any admin-table field. The patch in version 5.37.0 introduces explicit query-parameter sanitization at the controller and service boundary via three new primitives: `strictParam`, `addQueryParams`, and `addBodyParams`. Operator chains that traverse into restricted relational targets are now rejected before reaching the database.
Published: 2026-05-14T18:43:04.844Z
Updated: 2026-05-14T19:50:58.218Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-22707 |
vulnerable | 2026-06-08 07:51:13.648871 |
Strapi Upload Plugin MIME Validation Bypass via Content API
Strapi is an open source headless content management system. In Strapi versions prior to 5.33.3, the Upload plugin's Content API endpoints did not enforce the administrator-configured MIME type restrictions (`plugin.upload.security.allowedTypes` and `deniedTypes`). The same restrictions were correctly enforced on the Admin Panel upload path. The upload plugin's `enforceUploadSecurity` security check was invoked in the admin upload controller but was missing from the Content API controller. The Content API handlers `uploadFiles` and `replaceFile` (and the `upload` wrapper that dispatches to them) called the underlying upload service directly, bypassing both the magic-byte MIME detection and the configured allow/deny lists. An authenticated user with the Content API upload permission could therefore upload file types the administrator had explicitly disallowed, including HTML and SVG content. In deployments serving uploaded files from the same origin as the admin panel (default), an attacker could upload an HTML or SVG file that, when opened directly by an admin, executed JavaScript in the admin origin, enabling admin-session hijack and authenticated administrative actions against the admin API. The patch in version 5.33.3 introduces a shared `prepareUploadRequest` helper that wraps `enforceUploadSecurity` and is called from both the Content API and admin upload controllers, ensuring identical security policy enforcement on every upload entry point.
Published: 2026-05-14T18:40:22.080Z
Updated: 2026-05-14T19:40:11.102Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-22706 |
vulnerable | 2026-06-08 07:51:13.646214 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-22599 |
vulnerable | 2026-06-08 07:51:13.273281 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-64526 |
vulnerable | 2026-06-08 07:39:19.899359 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-53092 |
vulnerable | 2026-06-08 07:31:13.930629 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-3930 |
vulnerable | 2026-06-08 07:23:10.162250 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-25298 |
vulnerable | 2026-06-08 07:12:51.123871 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-56143 |
vulnerable | 2026-06-08 06:54:17.458996 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-52588 |
vulnerable | 2026-06-08 06:52:16.123105 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-34065 |
vulnerable | 2026-06-08 06:37:32.597157 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-31217 |
vulnerable | 2026-06-08 06:35:31.117486 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-29181 |
vulnerable | 2026-06-08 06:33:28.920149 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-39345 |
vulnerable | 2026-06-08 06:09:37.165251 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-38507 |
vulnerable | 2026-06-08 06:08:18.125972 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-37263 |
vulnerable | 2026-06-08 06:08:15.022263 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-36472 |
vulnerable | 2026-06-08 06:08:11.918270 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-34235 |
vulnerable | 2026-06-08 06:06:24.914347 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-34093 |
vulnerable | 2026-06-08 06:06:24.488669 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-22894 |
vulnerable | 2026-06-08 05:54:27.320108 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-22893 |
vulnerable | 2026-06-08 05:54:27.319786 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-22621 |
vulnerable | 2026-06-08 05:54:26.632061 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-31367 |
vulnerable | 2026-06-08 05:43:40.747774 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-30618 |
vulnerable | 2026-06-08 05:43:38.683485 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-30617 |
vulnerable | 2026-06-08 05:43:38.674409 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-29894 |
vulnerable | 2026-06-08 05:42:49.595565 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-0764 |
vulnerable | 2026-06-08 05:39:10.777974 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-46440 |
vulnerable | 2026-06-08 05:38:03.380988 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-28128 |
vulnerable | 2026-06-08 05:31:22.979208 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-27666 |
vulnerable | 2026-06-08 05:23:52.924112 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-27665 |
vulnerable | 2026-06-08 05:23:52.923714 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-27664 |
vulnerable | 2026-06-08 05:23:52.923291 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2020-13961 |
vulnerable | 2026-06-08 05:18:01.640433 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2019-19609 |
vulnerable | 2026-06-08 05:13:23.133265 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2019-18818 |
vulnerable | 2026-06-08 05:13:12.295254 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.