p PatchFirst

PatchFirst · Свежие уязвимости

apostrophe 4.33.0: известные уязвимости

Известных уязвимостей, затрагивающих apostrophe 4.33.0: 6. Сравните исправленные версии ниже с установленной у вас.

Фильтры уязвимостей
Сбросить фильтры

Уязвимостей: 6

  1. CVE-2026-113649

    Средний · CVSS 6.5EPSS 0,3%Есть исправление

    ApostropheCMS: Import API bypasses publication roles for protected content

    ApostropheCMS is an open-source Node.js content management system. Prior to 3.7.1 of the import-export module and 4.34.0 of core ApostropheCMS, an editor who can import an enabled content type but lacks its stronger publication role can cause import write helpers to create, replace, or remove published variants without the normal publish permission and lifecycle checks. This issue is fixed in import-export 3.7.1 and ApostropheCMS 4.34.0.

    • Обновитесь до 4.34.0
    Опубликовано Обновлено
  2. CVE-2026-112958

    Средний · CVSS 5.4EPSS 0,3%Публичный эксплойтЕсть исправление

    ApostropheCMS: Stored XSS via Unescaped Widget Style Attribute Serialization

    ApostropheCMS is an open-source Node.js content management system. Prior to 4.34.0, a project-defined free-form widget style field can carry an editor-controlled quote into an inline style attribute because the wrapper serializer does not apply HTML-attribute encoding. The quote can terminate the style attribute and inject executable attributes when published content, or an affected draft viewed by a higher-privileged user, is rendered. This issue is fixed in version 4.34.0.

    • Обновитесь до 4.34.0
    Опубликовано Обновлено
  3. CVE-2026-112957

    Средний · CVSS 4.3EPSS 0,31%Публичный эксплойтЕсть исправление

    ApostropheCMS: GET /api/v1/@apostrophecms/page/:id bypasses viewRole restriction and exposes viewPermission-gated fields to lower-privileged users

    ApostropheCMS is an open-source Node.js content management system. Prior to 4.34.0, the getOne REST endpoint for pages does not apply viewRole type-level restrictions or viewPermission field-level redaction. An editor-level user who knows a document _id can read the full content of admin-only pages and their privileged fields, while the getAll endpoint correctly enforces both restrictions. This issue is fixed in version 4.34.0.

    • Обновитесь до 4.34.0
    Опубликовано Обновлено
  4. CVE-2026-112954

    Средний · CVSS 5.3EPSS 0,44%Публичный эксплойтЕсть исправление

    ApostropheCMS: Unauthenticated publicApiProjection bypass via search and sort query builders in the public REST API

    ApostropheCMS is an open-source Node.js content management system. Prior to 4.34.0, a public REST API type that uses publicApiProjection can expose excluded searchable or sortable field information through search membership and sort ordering oracles. Returned fields remain filtered by the projection, so the issue permits targeted inference about hidden values rather than an unrestricted field dump. This issue is fixed in version 4.34.0.

    • Обновитесь до 4.34.0
    Опубликовано Обновлено
  5. CVE-2026-112952

    Средний · CVSS 4.3EPSS 0,33%Публичный эксплойтЕсть исправление

    ApostropheCMS: POST /api/v1/@apostrophecms/doc/slugTaken discloses existence of private/admin-only content to any authenticated user

    ApostropheCMS is an open-source Node.js content management system. Prior to 4.34.0, 'POST /api/v1/@apostrophecms/doc/slugTaken' with body { "slug": "target-slug" } returns a boolean indicating whether a slug is in use across all document types and visibility levels, with no permission or type filter. Any logged-in user (including editors) can enumerate the slug space of private pages, drafts, and archived content. This issue is fixed in version 4.34.0.

    • Обновитесь до 4.34.0
    Опубликовано Обновлено
  6. CVE-2026-112951

    Средний · CVSS 5.4EPSS 0,3%Публичный эксплойтЕсть исправление

    ApostropheCMS: Color field validation bypass allows stored XSS via HTML appended after rgb()/hsl() prefix

    ApostropheCMS is an open-source Node.js content management system. Prior to 4.34.0, the color field accepts trailing content after a valid rgb() or hsl() prefix because its TinyColor validation does not require the entire value to match a color. An authenticated user with edit rights can store arbitrary HTML after a valid color prefix. When the stored value is rendered, the payload executes, resulting in stored XSS. This issue is fixed in version 4.34.0.

    • Обновитесь до 4.34.0
    Опубликовано Обновлено

Проверьте свой сервер

Сопоставьте установленный стек и версии со свежими базами уязвимостей.

Проверьте свой сервер →