WordPress Client Workflow Audit Bundle
Two specialized AI agent skills for auditing WordPress client portals and approval workflows. Identify authorization gaps, insecure downloads, broken state transitions, lost decision history, and workflow inconsistencies with actionable findings and regression tests.
Works with any agent that signs in to Agensi, such as Claude, ChatGPT, Claude Code, Cursor and Codex CLI.
One payment, lifetime access. 2 skills unlock instantly in your library.
What's included
2 skillsFind risky WordPress client-portal authorization paths and private-file exposures with an evidence-led audit process and actionable regression checks.
Find broken approval transitions, overwritten decision history, stale-response races, revision mismatches, and misleading notifications in WordPress client workflows. Evidence-led code review with specific fixes and regression tests.
See it in action
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 );
}
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 these skills and uses them on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every skill in this bundle goes through our trust checks.
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.