WordPress SHA-256 Approval Check Explained
ملخص
Pixel shares a DEV Community article on a WordPress SHA-256 fix that checks whether a post’s title, content, and excerpt still match the version approved for publication. It explains why roles, revisions, and automation alone may not prevent last-minute or unauthorized edits, and how hash verification can help protect content integrity.
DEV Community
WordPress published a change nobody re-approved: the SHA-256 fix
WordPress published a change nobody re-approved: the SHA-256 fix A writer drafts. A reviewer signs it off. An hour before launch, somebody fixes "just a typo" — except the typo was the price in the third paragraph. The post still says approved. It still publishes. Nothing in that story is a permissions bug. The approval was a flag with no memory of what it approved. What actually breaks What the site has What it proves What it misses A status like approved, or "Editor can publish" Somebody pressed a button at some point Whether the text in the row is the text that was on screen then Revisions History exists after the fact Nothing stops the write; you find out from a client email A staging site A copy existed somewhere Production still accepts any edit, from anyone, at any time A hash of title + content + excerpt taken at approval This exact text was signed off Edits, and nothing else — see the limits below The first three answer "was this workflow followed?". Only the fourth answers "is this the text that was approved?". Why roles and permissions do not solve it Giving publish rights only to a reviewer controls who can publish. It says nothing about what. In practice the reviewer is the one making the last-minute edit half the time, and a second administrator — the agency, the VA, the intern with an app password — goes around the reviewer completely. The same hole exists in the other direction: an automation that gates publishing with an approval step is bypassed the moment a human publishes from wp-admin. If the check lives in the automation, the site is only protected for the people who use the automation. The mechanism On approval, store the SHA-256 of post_title + post_content + post_excerpt together, in post meta. On every save, recompute that hash from the incoming data, before the row is written. If the stored hash is missing, or does not equal the recomputed one, force the post back to draft. Show both hashes in an admin notice, so "which version was approved" is answerable instead of arguable. The hook is the whole argument for this design: wp_insert_post_data runs for the classic editor, the block editor, the REST API, quick edit and bulk edit. A save that goes through WordPress goes through that filter — which is why the check belongs there, not in admin-side validation or a JavaScript guard. // Simplified excerpt - a real plugin does the bookkeeping around this.
add_filter( 'wp_insert_post_data', function ( $data, $postarr ) {
$post_id = (int) ( $postarr['ID'] ?? 0 );
if ( ! $post_id || 'publish' !== $data['post_status'] ) {
return $data; // only a publish attempt is gated
}
$approved = get_post_meta( $post_id, '_sag_approved_hash', true );
if ( '' === $approved ) {
return $data; // never approved: not this check's business
}
$current = hash( 'sha256',
$data['post_title'] . "\n" . $data['post_content'] . "\n" . $data['post_excerpt']
);
if ( ! hash_equals( $approved, $current ) ) {
$data['post_status'] = 'draft'; // publish refused
set_transient( 'sag_blocked_' . $post_id, array(
'approved' => $approved,
'current' => $current,
), 60 );
}
return $data;
}, 10, 2 );
Two details matter more than they look: hash_equals, not ===. Cheap, and it keeps the comparison constant-time out of habit. The check only fires on a publish attempt. Drafts and autosaves must stay cheap and must never be silently rewritten, or editors will (rightly) hate it. What it does not cover — say this out loud Images and custom fields. The hash covers the three text fields. Swap the featured image after approval and the hash does not move. Judgement. It cannot tell a good edit from a bad one. It only says this is not what was signed off. Render-time changes. A template edit, a shortcode or a plugin that rewrites output later is outside the check. Friction. It will annoy somebody exa...

Powered by Readybot.io