Weekly News Roundup

One Letter in the Wrong Case Left the Lock Open — A PHP Flaw Hidden for About 20 Years, and the WordPress Check

Security Lab — kurashiki-bouzu

Hello, I am Kurashiki Bouzu (kurashiki-bouzu), born in 1971. I am a former funeral director, and I now live in an old house in Kurashiki, Okayama, working together with my AI butler, Moka (Muse).

This is a story about a single letter. Uppercase or lowercase — that alone decided whether the lock was on or off. If you run a website, this one is about you, so please read it that way.

The result first

Here is the conclusion, up front.

What happened — the “s” is the mark of the lock

Look at the head of a web address: “https”. The last “s” is the mark that says “this connection is locked.” With the lock on, even if someone peeks in along the way, they cannot read the contents.

But when PHP opened an outside address, it decided whether to apply the lock by looking for a lowercase “s” in a fixed position.

If the last letter was uppercase — “httpS://” or “HTTPS://” — it missed the mark of the lock. And so it sent the data as a plain, unlocked connection. That was the flaw.

Think of a house. It is as if you checked whether you had locked up by the shape of the letters on your nameplate. The moment the name was written in an unfamiliar shape, you assumed “this house needs no lock” and left it wide open. Simple — and frightening.

What is dangerous about it

In an unlocked connection, passwords, the passphrases machines use in place of a login (tokens), and the contents you send all flow as they are. If someone steals a look in transit, they can read everything.

Redirects had the same problem. If a locked connection automatically forwarded you to an uppercase address, the contents and the login information carried over were sent without the lock.

To be honest, though: exploiting this needs two conditions to line up.

  1. An address containing an uppercase “S” reaches the machinery
  2. Someone is in a position to peek at the traffic in transit

So this is not a case of “every site is in danger right now.” There is no need to panic. But now that the fix is out, checking is worth the minute it takes.

The flaw received a worldwide ID number: “CVE-2026-128064.” Its severity is rated “High” — the second of four levels.

Hidden for about 20 years

How long had this flaw been there? For addresses handed over by programs: since “PHP 5.2.0,” that is, 2006. For redirects: since “PHP 4.3.0,” in 2002.

About 20 years. The people who found it seem to have been astonished themselves — the Mado no Mori article closed with a sigh to that effect, and I feel the same. Big flaws in big machinery usually wear complicated faces. This one was just the difference between an uppercase and a lowercase letter.

The fix is already out

On November 19, 2026, a PHP update shipped and repaired 17 weaknesses, this flaw among them. The fixed versions are:

If you cannot update right away, workarounds are published too: keep the head of addresses in lowercase, and stop automatic redirects so you can check where one leads before following it.

The WordPress angle — “a PHP story” is “a story about your own site”

From here, this is for people who run a site.

WordPress runs on PHP. According to the research firm W3Techs, about 40% of all websites in the world (39.4% as of November 2026) are WordPress. Which means “my PHP version is old” can translate directly into “the foundation of my own site is old.”

There is a worrying number, too. About a third of WordPress sites still run PHP 8.1 or older (WordPress.org statistics). Versions 8.1 and earlier no longer receive new fixes — this one included. The fix reaches only 8.2 and later.

You can update WordPress itself from its admin screen. But the PHP version is not WordPress’s business; it belongs to the server the site sits on. Mix those two up, and you get “but WordPress is up to date, so why…?”

What a site owner can do today

One step at a time is fine.

1. Check your PHP version

On WordPress, open “Site Health” in the admin screen and you can see the PHP version in use. Start by knowing your own number.

2. Compare it with the fixed versions

Compare with the list above. If your line is at or past its fixed version, this flaw is repaired for you.

3. On a rental server, read the notices

If your site runs on a rented server, check the server company’s announcements. The operation to raise the PHP version is usually provided in the server’s admin screen. If it is unclear, asking the company “I would like to raise my PHP version to a fixed release” is quite enough.

4. If you are on 8.1 or older, plan the upgrade

No fixes arrive for 8.1 or earlier. Upgrading is itself a protection. But whether your theme and plugins will run on the new version needs checking as you go, so plan it in steps. Here, too, asking your server company or the person who built your site is the shortcut.

5. Do not panic

To repeat: this flaw cannot be exploited unless the conditions line up. Nothing here says to take your site down today. Check the version, and raise it in order. That is enough.

Do not overlook small differences

Uppercase and lowercase. A single letter’s difference left connections unlocked for about 20 years.

The basics of protection are not difficult: check the small differences, and when a fix comes out, install it. It connects with what I wrote on the main blog in the weekly news roundup — “do not put updates off.”

This time, the star was an update on the server side. Which version is your own site’s foundation running right now? I would be glad if this article became the nudge to check.

Notes

Sources checked


Entrance (other languages)

日本語 中文 Español 한국어 Français Deutsch हिन्दी العربية

Weekly News Roundup / Back to the English top