Security context

What an agent needs to avoid regressing past fixes and find the next vuln in this repo.

WordPress/gutenberg
trunk @ bfb6e57
68
Fixes
0
CVEs
HIGH
Peak severity
19.4%
Coverage
Highlights
Auth Bypass: 27 prior fixes. Scrutinize any change in this area.
lib/compat/wordpress-7.0/class-wp-http-polling-sync-server.php: most-fixed (4 issues). Treat as high-risk during review.
41 high-severity fixes in this history; regressions here are high-impact.
Recurring patterns

The bug types that recur here, drawn from past fixes, not open vulnerabilities.

Auth Bypass: Multiple fixes (4) target this component, indicating persistent authorization gaps in the sync server's permission checks for posts, terms, comments, and collections. The fixes added capability checks, object ID validation, and room pattern validation, but the repeated patches suggest incomplete coverage.
Auth Bypass: Four fixes in the guidelines feature show a pattern of incomplete permission checks across post type registration, REST controllers, and revisions. The fixes added capability checks and restricted deletion to admins, but the spread across components indicates a systemic issue.
Auth Bypass: Two fixes added permission checks for delete/restore/rename and duplicate actions, showing that client-side actions were exposed without capability validation. The fixes use canUser, but the pattern suggests other action types may still be missing checks.