wp-plugin-rest-auth-bypass

Scan WordPress REST API plugin endpoints for unauthenticated state-changing operations.

3|1|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/EntroVyx/hermes-agent-offsec --skill wp-plugin-rest-auth-bypass-entrovyx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wp-plugin-rest-auth-bypass
Source: https://github.com/EntroVyx/hermes-agent-offsec/tree/main/skills/offsec/recon/wp-plugin-rest-auth-bypass
Command: npx skills add https://github.com/EntroVyx/hermes-agent-offsec --skill wp-plugin-rest-auth-bypass-entrovyx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, requests.

What problem does it solve?

This skill addresses the security risk of WordPress plugins that expose sensitive state-changing REST API endpoints without proper authentication, allowing unauthorized users to modify site settings or publish content.

Core Features & Use Cases

  • Namespace Enumeration: Automatically discovers third-party plugin REST API namespaces.
  • Route Mapping: Maps all available endpoints for identified plugins to reveal hidden functionality.
  • Vulnerability Testing: Probes POST, PUT, PATCH, and DELETE methods to confirm if endpoints are accessible without authentication.

Quick Start

Use the wp-plugin-rest-auth-bypass skill to scan the target website at https://example.com for unauthenticated REST API vulnerabilities.

Frequently Asked Questions about wp-plugin-rest-auth-bypass

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan WordPress REST API endpoints for unauthenticated access vulnerabilities?

Scanning WordPress REST API endpoints involves mapping custom plugin namespaces and probing POST, PUT, PATCH, and DELETE methods to confirm if endpoints allow unauthorized access. This automated HTTP probing detects security misconfigurations exposing state-changing operations.

What WordPress REST API security misconfigurations allow unauthorized content publishing or settings modification?

Security misconfigurations in custom plugin REST API namespaces allow unauthorized content publishing and settings modification by failing to enforce authentication on state-changing operations. Probing endpoints with HTTP methods like POST and DELETE reveals these unauthorized access vectors.

Do I need python3 and the requests library to test WordPress plugin REST API routes?

Yes, testing WordPress plugin REST API routes requires python3 and the requests library to execute automated HTTP method probing. These dependencies handle sending requests to map endpoints and probe for unauthenticated state-changing operations.

How does namespace enumeration discover hidden WordPress REST API functionality?

Namespace enumeration discovers hidden WordPress REST API functionality by automatically identifying third-party plugin namespaces. Route mapping then identifies all available endpoints within those namespaces, revealing undocumented operations accessible via the API.

What HTTP methods should be tested to detect unauthenticated WordPress REST API data leakage vectors?

Testing POST, PUT, PATCH, and DELETE HTTP methods detects unauthenticated WordPress REST API data leakage vectors by confirming if state-changing operations are accessible without authentication. This probing reveals unauthorized access to sensitive content publishing and settings modification.