Urgent.News

What's breaking now, across thousands of outlets.

Tech

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…

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.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

AER-1: the open standard for agent execution receipts

A standard is not a document. A document plus a published test corpus, plus independent implementations written by people who owe you nothing, plus a production stream anyone can audit: that is a…

  • AER-1 is an open standard for agent execution receipts defined in IETF Internet-Draft
  • Brennan Zambo created AER-1 based on a document and test corpus
  • 140,344 public AER-1 receipts minted as of November 15, 2026

GLIBCXX_3.4.29 not found - and why copying libstdc++ does not fix it

Short answer GLIBCXX_3.4.29 is a version tag in libstdc++ (the C++ standard library shipped with GCC), not in glibc. The binary was built with a newer GCC than the target host has, so the target's…

  • "GLIBCXX3.4.29 not found" error occurs due to version mismatch between binary and C library.
  • Copying libstdc++ file does not fix the issue, deeper glibc error persists.

Idempotent publishing jobs #h9q2z

Every job gets an id and a state machine: queued, running, retry, published. Deduplicate by job id before writing a publication record. Related Source repository Mbin instance Author profile on DEV

More from Sunday 15 November →