Works with the AI Agents you already use
Wordpress Client Portal Security Audit
Find risky WordPress client-portal authorization paths and private-file exposures with an evidence-led audit process and actionable regression checks.
$19
Wordpress Client Portal Security Audit
Example session with this skill installed
Audit my WordPress plugin for client-portal security issues.
I want a focused review of authorization, client isolation, protected file downloads, nonce/capability checks, AJAX/REST/admin-post handlers, and any places where one client could access another client’s data.
Please review the relevant PHP code and identify only real, reachable problems. For each issue, give:
- severity
- affected file and code path
- attack/failure scenario
- why it is a real security issue
- the smallest appropriate fix
- a regression test idea
Do not give generic WordPress advice unless it applies to the code. Prioritize:
- cross-client data leaks
- insecure file access
- missing capability checks
- nonce misuse
- stored/reflected XSS in portal or admin views
- unsafe redirects or request handling
Return a concise report with a summary, findings table, detailed findings, and next steps.
- Read your context and instructions
- Compiled the wordpress client portal
Summary
I reviewed the plugin for client-portal security risks, with emphasis on client isolation, protected downloads, request handlers, and WordPress authorization patterns.
I found
3 actionable security issues:
1 high,
1 medium, and
1 low. The highest-risk issue allows a logged-in client to access another client’s protected file by changing an ID in the request. I also found a state-changing handler that validates a nonce but does not enforce a capability/ownership check, and one output path where user-controlled content should be escaped more strictly.
Findings overview
| Severity | Issue | File / Area | Risk |
|---|---|---|---|
| High | Direct object reference in protected download flow | includes/class-client-files.php → download handler | One client may access another client’s private file |
| Medium | Nonce used without full authorization check | includes/class-client-actions.php → approval action handler | Logged-in user may trigger state changes on records they do not own |
| Low | Incomplete output escaping for note content | admin/views/request-history.php | Stored XSS risk in admin/client-facing history UI |
Detailed findings
1. High — Protected file download does not fully verify ownership
Where: includes/class-client-files.php in the request path that reads file_id and serves a protected download.
What happens:
The handler validates the request and loads the file record by ID, but the final authorization check is based only on the existence of the file and the current logged-in state. It does not consistently verify that the file belongs to the same client account as the requester.
Attack scenario:
A logged-in client downloads their own file, notices a numeric file_id, then changes it to another valid ID. If the second file exists, the handler may serve it even though it belongs to another client.
Why this is a real issue:
This is a classic IDOR / broken object-level authorization problem. In a client portal, per-client isolation is a core security requirement.
Smallest appropriate fix:
Resolve the current user’s client identity first, then enforce an ownership match before serving the file.
$file_id = absint( $_GET['file_id'] ?? 0 );
$client_id = myplugin_get_current_client_id();
$file = myplugin_get_file( $file_id );
if ( ! $file || ! $client_id || (int) $file->client_id !== (int) $client_id ) {
wp_die( esc_html__( 'You are not allowed to access this file.', 'your-text-domain' ), 403 );
}
Connects securely to your tools. The creator never sees your data.
About this skill
WordPress Client Portal Security Audit
Find authorization gaps, protect private client data, and review WordPress security with confidence.
Building a WordPress client portal involves more than protecting a login page.
When your plugin handles private documents, client approvals, confidential messages, or user-specific content, a single missing ownership check can expose sensitive information to the wrong person.
WordPress Client Portal Security Audit is a specialized AI agent skill that helps developers identify real security risks in WordPress plugins before they become production problems.
Instead of producing generic security advice, it guides your AI coding assistant through a structured, evidence-based review of your plugin's PHP code, WordPress permissions, private file handling, and client-specific workflows.
🔐 What This Skill Audits
1. Client Isolation & Authorization
Ensure that users can access only the information they're authorized to see.
- Cross-client data exposure
- Insecure Direct Object References (IDOR)
- Broken Object-Level Authorization (BOLA)
- Missing ownership checks
- Unsafe post, user, attachment, and metadata access
- Role and capability enforcement
- Authorization gaps in nested resources
2. Protected File Downloads
Review the complete path from a download request to the actual file response.
- Unauthorized access to private attachments
- Direct URL bypasses
- Missing client-to-file ownership verification
- Path traversal and unsafe file paths
- Insecure file-serving endpoints
- Access after reassignment, deletion, expiration, or session revocation
3. WordPress Request Handlers
Inspect security-sensitive entry points, including:
- WordPress REST API endpoints
- AJAX handlers
admin-post.phpactions- Form submissions
- Custom download handlers
- Privileged hooks and callbacks
The skill verifies that authentication, authorization, nonce validation, and input handling are applied appropriately.
Important: A valid WordPress nonce does not replace a permission or ownership check.
4. Input Validation & Output Security
Identify reachable issues involving:
- Stored and reflected cross-site scripting (XSS)
- Incorrect output escaping
- Unsafe redirects
- Untrusted request parameters
- Insecure SQL handling
- Sensitive data exposure through errors or logs
5. Approval Workflow Security
For plugins that handle client decisions, the skill also examines:
- Unauthorized approve/reject actions
- Cross-client request manipulation
- Responder identity validation
- Workflow state changes
- Security-sensitive notification and history behavior
📋 What You Receive
The skill produces a structured security review that developers can act on immediately.
Each confirmed finding includes:
- Severity — Critical, High, Medium, or Low
- Location — Relevant file, function, and line number when available
- Security impact — What could go wrong and who could be affected
- Evidence — The code path supporting the finding
- Failure scenario — How the issue could occur
- Recommended fix — The smallest appropriate correction
- Regression test — How to prevent the same issue from returning
Findings requiring additional verification are explicitly distinguished from confirmed issues.
No invented vulnerabilities. No generic checklist padding. No unnecessary refactoring recommendations.
🧠 More Than a Generic Security Prompt
This is a structured review workflow designed specifically around WordPress development.
The package includes:
- A ready-to-use
SKILL.mdwith an end-to-end audit procedure - WordPress authorization and permission guidance
- Client isolation and trust-boundary guidance
- Protected download security checks
- Approval workflow safety guidance
- Practical regression-test scenarios
- A reusable security audit report template
- A worked example demonstrating the expected review format
- An optional read-only Python scanner for identifying security-sensitive PHP entry points
The optional scanner helps locate code worth inspecting. It does not automatically classify vulnerabilities or replace the evidence-based review.
👨💻 Who Is This For?
WordPress Plugin Developers
Review custom plugins before release or after implementing security-sensitive changes.
Freelancers
Improve the quality of client portal implementations and identify overlooked authorization risks.
WordPress Agencies
Review plugins managing multiple clients, private content, approvals, and documents.
AI-Assisted Developers
Give your coding assistant a repeatable specialist procedure instead of relying on a broad request such as "check my plugin for security issues."
🚀 How to Use It
Step 1 — Install the skill
Add the provided skill package to your compatible AI coding assistant.
Step 2 — Open your WordPress plugin project
Give the agent access to the source code you're authorized to review.
Step 3 — Request an audit
Example:
Audit this WordPress plugin for client isolation and protected download vulnerabilities. Trace authorization from each request handler to the underlying resource. Report confirmed issues with file locations, failure scenarios, recommended fixes, and regression tests. Do not modify files.
Step 4 — Review the findings
Use the prioritized report to inspect vulnerabilities, implement fixes, and plan regression tests.
Step 5 — Repeat after meaningful changes
Run a targeted review after modifying permissions, download handlers, client assignments, or approval workflows.
✅ Designed for Safe, Focused Reviews
- Read-only by default: Does not modify project files.
- Evidence-first: Requires traceable code evidence for confirmed findings.
- WordPress-specific: Understands capabilities, nonces, REST permissions, and plugin architecture.
- Developer-friendly: Prioritizes actionable issues and minimal fixes.
- Scope-aware: Reviews relevant code without requiring an unnecessary full-project scan.
- No external service required: Analysis can be performed locally with an appropriately configured coding agent.
Known Limitations
This is an AI-assisted static source-code review skill, not an automated penetration-testing service.
It cannot guarantee the detection of every vulnerability or certify that a plugin is secure. Findings should be reviewed by a qualified developer, and security-sensitive fixes should be verified through appropriate testing.
The optional local scanner requires Python 3.9+ and explicit permission to run commands. The core skill does not require the scanner.
🛡️ Build Client Portals With Better Security Practices
A client portal should protect every client's data—not just hide it behind a login page.
WordPress Client Portal Security Audit helps you examine the authorization boundaries that matter, identify potential vulnerabilities, and turn findings into concrete fixes and regression tests.
Install the skill, review your code, and make security part of your WordPress development workflow.
- Static analysis only: Reviews source code and configuration; does not perform live penetration testing, execute exploits, or scan a running website.
- Source code access required: The AI agent needs access to the relevant WordPress plugin files to produce meaningful findings.
- AI-assisted findings: Results may include false positives or miss vulnerabilities. Findings should be verified by a qualified developer before applying fixes.
- Focused scope: Specializes in WordPress client portals, authorization, client isolation, protected downloads, and request handlers. It is not a complete WordPress security audit.
- No automatic remediation: Provides prioritized findings, suggested fixes, and regression-test recommendations. It does not automatically modify production systems.
- No security guarantee: Using this skill does not certify a plugin as secure or replace professional security testing.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 15 days ago
Permissions
Requires read-only access to the WordPress plugin source files that the user explicitly authorizes for review, including relevant PHP files, configuration, and documentation. Includes an optional Python 3.9+ static scanner that can be executed locally only with the user's permission. The scanner reads PHP source files and reports potential security-sensitive code locations without modifying files. The skill does not require file-writing permissions, browser access, network access, environment variables, API keys, credentials, or external services. All analysis is limited to the authorized project. No production data access, live exploitation, or external data transmission is required.