<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[🚨 Hey, so that nginx RCE targeting instances with the unnamed rewrite rule?]]></title><description><![CDATA[<p><img src="https://board.circlewithadot.net/assets/plugins/nodebb-plugin-emoji/emoji/android/1f6a8.png?v=28325c671da" class="not-responsive emoji emoji-android emoji--rotating_light" style="height:23px;width:auto;vertical-align:middle" title="🚨" alt="🚨" /> Hey, so that nginx RCE targeting instances with the unnamed rewrite rule? =&gt; It's extremely common.</p><p>That exact rule is the official recommended config from Yoast for their XML sitemaps on NGINX.</p><p>From their help page:</p><p>rewrite ^/([^/]+?)-sitemap([0-9]+)?.xml$ /index.php?sitemap=$1&amp;sitemap_n=$2 last;</p><p>This is copy-pasted verbatim by millions of WP sites running Yoast SEO (5+ million active installs) and also by sites using other SEO plugins that followed Yoast's lead. (1/3)</p>]]></description><link>https://board.circlewithadot.net/topic/8154132a-3737-4837-9615-7c2c795ceb2a/hey-so-that-nginx-rce-targeting-instances-with-the-unnamed-rewrite-rule</link><generator>RSS for Node</generator><lastBuildDate>Fri, 15 May 2026 04:02:51 GMT</lastBuildDate><atom:link href="https://board.circlewithadot.net/topic/8154132a-3737-4837-9615-7c2c795ceb2a.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 14 May 2026 12:08:10 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to 🚨 Hey, so that nginx RCE targeting instances with the unnamed rewrite rule? on Thu, 14 May 2026 13:13:10 GMT]]></title><description><![CDATA[<p>OH, and FWIW the White House runs WordPress on nginx and likely has a plugin running that causes the weak nginx rewrite rule to be needed.</p>]]></description><link>https://board.circlewithadot.net/post/https://mastodon.social/users/hrbrmstr/statuses/116573103078221129</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://mastodon.social/users/hrbrmstr/statuses/116573103078221129</guid><dc:creator><![CDATA[hrbrmstr@mastodon.social]]></dc:creator><pubDate>Thu, 14 May 2026 13:13:10 GMT</pubDate></item><item><title><![CDATA[Reply to 🚨 Hey, so that nginx RCE targeting instances with the unnamed rewrite rule? on Thu, 14 May 2026 12:09:51 GMT]]></title><description><![CDATA[<p>I still had a lingering nginx box with a legacy WP config (and un-upgrade-able nginx)I had to find and fix, hence the script.</p>]]></description><link>https://board.circlewithadot.net/post/https://mastodon.social/users/hrbrmstr/statuses/116572854108585135</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://mastodon.social/users/hrbrmstr/statuses/116572854108585135</guid><dc:creator><![CDATA[hrbrmstr@mastodon.social]]></dc:creator><pubDate>Thu, 14 May 2026 12:09:51 GMT</pubDate></item><item><title><![CDATA[Reply to 🚨 Hey, so that nginx RCE targeting instances with the unnamed rewrite rule? on Thu, 14 May 2026 12:08:11 GMT]]></title><description><![CDATA[<p>PRs/helpful suggestions/credit to it from skeezy cyber vendors who steal it and put it in their products without compensation is welcome/encouraged (3/3)</p>]]></description><link>https://board.circlewithadot.net/post/https://mastodon.social/users/hrbrmstr/statuses/116572847558280529</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://mastodon.social/users/hrbrmstr/statuses/116572847558280529</guid><dc:creator><![CDATA[hrbrmstr@mastodon.social]]></dc:creator><pubDate>Thu, 14 May 2026 12:08:11 GMT</pubDate></item><item><title><![CDATA[Reply to 🚨 Hey, so that nginx RCE targeting instances with the unnamed rewrite rule? on Thu, 14 May 2026 12:08:10 GMT]]></title><description><![CDATA[<p>The EasyEngine tutorial, StackPointer, WPMU DEV, Stack Overflow, and the WordPress.org forums all reference this same pattern.</p><p>This can easily be chained with one (or both) of two recent and trivial-to-exploit local privilege escalation Linux vulns.</p><p>In the words of <span><a href="/user/krypt3ia%40infosec.exchange">@<span>krypt3ia</span></a></span> :</p><p>we doomed.</p><p>HOWEVER: I threw together a small Bash script that tries to detect whether a given conf file or directory of nginx configs has vulnerable directives. You can find it at:</p><p><a href="https://git.sr.ht/~hrbrmstr/cve-2026-42945-scanner…" rel="nofollow noopener"><span>https://</span><span>git.sr.ht/~hrbrmstr/cve-2026-4</span><span>2945-scanner…</span></a> (2/3)</p>]]></description><link>https://board.circlewithadot.net/post/https://mastodon.social/users/hrbrmstr/statuses/116572847528970537</link><guid isPermaLink="true">https://board.circlewithadot.net/post/https://mastodon.social/users/hrbrmstr/statuses/116572847528970537</guid><dc:creator><![CDATA[hrbrmstr@mastodon.social]]></dc:creator><pubDate>Thu, 14 May 2026 12:08:10 GMT</pubDate></item></channel></rss>