Wp Xmlrpc Exposed
WordPress: /xmlrpc.php exposed (brute-force amplification + DDoS reflector + auth-bypass surface).
One of 122 modules in the GateTest scan suite. Catches the issue before it reaches code review, and on paid tiers opens a pull request with the fix already written.
/xmlrpc.php returns 200 — disable or block at WAF
Why we catch it
OWASP-grade scanning that goes beyond CVE lookups into your actual code paths.
The Wp Xmlrpc Exposed module sits in this category alongside 6 related modules. Together they form one of the layers of a GateTest scan — checks fire in parallel, findings cluster by root cause, and on paid tiers the AI auto-fix loop reads each finding, writes the fix, validates against the scanner, and opens a PR.
How GateTest covers wp xmlrpc exposed
- Runs against a live URL. The live-URL scanners, not the repository tiers: the website scan ($29 full report) and the WordPress health check ($19). It probes a running site, so it needs a URL rather than a repo. No additional configuration.
- Free CLI.
npm i -g @gatetest/cli && gatetest --crawl https://your-site.example --module wpXmlrpcExposedagainst a site you own. No paywall on the scanning itself. - AI auto-fix PR. Live-URL findings come with plain-English fix instructions. Auto-fix pull requests are for repository findings on the Scan + Fix and Forensic tiers.
- Honest confidence rating. Findings come with high / medium / low confidence so noisy patterns don't block the gate. The confidence-calibrator trainer reads customer suppressions and tightens rules over time.
Scan your repo for wp xmlrpc exposed
Free preview of the headline findings. Pay per scan, not per seat — one-time scans never auto-renew.
Frequently asked questions
What does the Wp Xmlrpc Exposed module catch?
WordPress: /xmlrpc.php exposed (brute-force amplification + DDoS reflector + auth-bypass surface). Example finding: /xmlrpc.php returns 200 — disable or block at WAF
Does GateTest fix Wp Xmlrpc Exposed issues automatically?
Live-URL findings ship with plain-English fix instructions and, where the platform allows it, a generated config file. Auto-fix pull requests are written for repository findings on the Scan + Fix ($199) and Forensic ($399) tiers.
Which tiers include the Wp Xmlrpc Exposed module?
The live-URL scanners, not the repository tiers: the website scan ($29 full report) and the WordPress health check ($19). It probes a running site, so it needs a URL rather than a repo.
Can I run the Wp Xmlrpc Exposed module from the CLI for free?
Yes — install with `npm i -g @gatetest/cli` and run `gatetest --crawl https://your-site.example --module wpXmlrpcExposed`. The local CLI is free; paid tiers add AI auto-fix and the cross-finding correlation work.