Urgent.News

What's breaking now, across thousands of outlets.

Tech

WordPress Gets Scanned Every Hour. Core Does Nothing About It.

WordPress runs a huge share of the web, and that popularity cuts both ways: it also makes WordPress the single most-scanned CMS on the internet. Every hour, bots are quietly probing for wp-config.php.bak , hammering xmlrpc.php , trying default admin paths, and stuffing SQL injection attempts into every form field they can find. WordPress core has no real answer to any of this — it assumes your…

WordPress, which powers a significant portion of the internet, is the most frequently scanned content management system (CMS) online. Every hour, bots relentlessly scan for weaknesses, attempting to exploit common vulnerabilities like the hidden backup file wp-config.php.bak, the XML-RPC API, and default admin paths. Despite this constant threat, WordPress core itself does not provide robust protection.

Instead, it relies on the security measures implemented by individual hosting providers, security plugins, or good fortune. To address this gap, a new plugin called xZeroProtect has been developed. This firewall sits between every incoming request and WordPress, analyzing it against a set of rules designed to detect known scanners, exploit tools, SQL injection attempts, and other malicious activity.

If a request matches any of these rules, it is automatically blocked and logged. While rate-limited attacks from repeat offenders may be banned, legitimate visitors are allowed through. One of the key benefits of xZeroProtect is its ability to distinguish between automated bots like Googlebot and human traffic. By verifying Googlebot and other major crawlers through double-DNS resolution, the plugin ensures that these legitimate sources are not mistakenly blocked by rate-limiting or other security measures.

Additionally, xZeroProtect does not rely on external services, databases, or complex configurations, making it suitable for most shared hosting environments. The plugin operates purely at the request level, working before WordPress routes the request, which means it does not interfere with other plugins or WordPress features. It also operates in a "learning mode" that logs potential violations without blocking them, allowing site owners to review and fine-tune the settings before fully activating the firewall.

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

Hardening an AWS EKS cluster: IRSA, NetworkPolicies, restricted Pod Security and Secrets Manager via CSI

A freshly created EKS cluster works, but it's permissive. Every pod can reach every other pod, workloads can run as root, and the easy way to give an application AWS access is to attach permissions to…

  • Implement IAM Roles for Service Accounts (IRSA) for least-privilege IAM role assumption
  • Use NetworkPolicies to enforce default-deny traffic within orders namespace
  • Utilize Secrets Store CSI driver to mount AWS Secrets Manager secrets as files

Run GLM-5.3-Flash (321B) locally with Project Maya and EXL3 on one RTX 5090

GLM-5.3-Flash is a 321B mixture-of-experts model, and its 3.05 bpw EXL3 quant is 125 GB, too big to fit in my workstation's 128 GB of RAM next to the OS.

  • GLM-5.3-Flash 321B model runs locally on RTX 5090 GPU
  • Project Maya fork used for installation and setup
  • 3.05 bits per word quantization allows model to fit in RAM

Framejury, a culling assistant that works offline and explains every photo it rejects

This is a submission for the Hacktoberfest Open-Source AI Challenge Week 2: Side Hustle What I Built Framejury looks through a folder of event photos, groups the frames that were shot seconds apart…

  • Framejury is an open-source offline photo culling assistant
  • Analyzes event photos to group similar shots and select best frames
  • Provides transparent explanations for each rejection decision

Making invoice PDFs in the browser: page breaks, money maths and one trade-off

I run a free invoice generator, PDF Bill Builder . The PDF is built entirely in the visitor's browser, so nothing is uploaded unless they sign in to save a document. Three problems took longer than I expected. Here is how each one ended up. 1. Render the preview, then slice it The design lives in one React component: the live preview.

More from Friday 16 October →