Kestrel
대시보드로 돌아가기
CVE-2026-50280MEDIUMMITRENVDGHSA대응게시일: 2026. 07. 01.수정일: 2026. 07. 02.

Craft CMS: Authorization bypass in `entries/move-to-section` via missing target-section save check

위협 신호 · CVSS · EPSS · KEV

정기 패치· 높은 악용 신호 없음
CVSS
medium

이론적 심각도 점수

EPSS
0.3%상위 80.6%

30일 내 악용 확률 예측

KEV
미등재

실측 악용 기록 없음

권장 대응 기한60일 이내CISA SSVC 기준

계획된 패치 주기 내 조치(60일 이내)

외부 노출· KEV 미등재 · 자동화 어려움 · 부분 영향 · 외부 노출

CVSS 벡터 · 메트릭

CVSS 벡터 정보 없음

상세 설명

Summary

The EntriesController::actionMoveToSection() endpoint checks only whether the current user can view the destination section, but it does not require permission to save entries into that section. A low-privileged authenticated control-panel user who can move an entry out of its current section can therefore move that entry into a different section where they have read access but no write access.

Details

The vulnerable route is implemented in EntriesController.php:465:

The destination check is only viewEntries:$section->uid . The source-entry gate is Entry::canMove(), which verifies whether the user can move the existing entry based on the source section:

This closes the exploit chain:

  1. External source: authenticated CP request to entries/move-to-section.
  2. Missing authorization check: destination section requires only viewEntries, not saveEntries.
  3. Privileged sink: moveEntryToSection() rewrites sectionId and saves the entry into the unauthorized section.

Preconditions derived from the code:

  1. The attacker is authenticated to the control panel.
  2. Entry 345 is movable by the attacker from its current section.
  3. The attacker can satisfy viewEntries on destination section 12.
  4. The attacker does not have saveEntries:DESTINATION_UID, which is the missing check that makes the bypass possible.

Result:

  1. The controller accepts the request because viewEntries:$section->uid passes.
  2. Each source entry passes canMove() based on source-section permissions.
  3. moveEntryToSection() updates the entry’s sectionId and saves it.
  4. The entry is now located in a section where the attacker did not have write permission.

Impact

This breaks the intended section-level authorization model. A user with limited content permissions can inject or relocate content into a protected section, interfering with editorial boundaries, approval workflows, section-specific business logic, and content ownership expectations.

AI 심층 분석

공격 시나리오 · 재현 가능한 PoC 페이로드 · 즉시 적용 가능한 차단 패치를 한 번에 받아 보세요. 보안 운영팀이 그대로 점검·티켓팅에 쓸 수 있는 형태로 정리해 드립니다.