{
  "id": 20238536,
  "title": "WordPress published a change nobody re-approved: the SHA-256 fix",
  "url": "https://urgent.news/2026/11/15/wordpress-published-a-change-nobody-re-approved-the-sha-256-fix",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-15T23:40:27.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/perun_automation/wordpress-published-a-change-nobody-re-approved-the-sha-256-fix-432c"
  },
  "original_language": "en",
  "account": "WordPress rolled out a SHA-256 fix change without proper approval. A typo was caught at the last minute, but the post still displayed as approved and went live. The approval flag had no memory of what it approved. The issue lies in the approval process itself, not a permissions bug. The approval status, like \"approved\" or \"Editor can publish,\" does not guarantee the actual content that was approved. The site accepts any edit from anyone at any time, as evidenced by revisions history. On approval, the SHA-256 of post_title, post_content, and post_excerpt should be stored in post meta. Every save recomputes the hash from the incoming data before writing to the database. If the stored hash doesn't match the recomputed one, the post should revert to draft status. This check should be implemented in wp_insert_post_data filter, which applies to the classic editor, block editor, REST API, quick edit, and bulk edit. The hash comparison should use hash_equals for a constant-time comparison. The solution addresses only the text fields and does not cover images or custom fields. It also doesn't differentiate between good and bad edits or template edits, shortcodes, or plugins that rewrite output later.",
  "summary": "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…",
  "key_points": [
    "WordPress published SHA-256 fix change without approval",
    "Approval process flawed, doesn't guarantee content approval",
    "Fix addresses text fields, not images or custom fields"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}