AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Wordpress Security

skill-iwritec0de-wp-dev-wordpress-security · by iwritec0de

>-

No reviews yet
0 installs
27 views
0.0% view→install

Install

$ agentstack add skill-iwritec0de-wp-dev-wordpress-security

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-iwritec0de-wp-dev-wordpress-security)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
5mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Wordpress Security? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

WordPress Security Best Practices

This skill covers WordPress security patterns including output escaping, input sanitization, nonce verification, capability checks, and secure database queries.

Output Escaping

Every piece of dynamic data rendered in HTML must be escaped. Choose the function matching the output context:

| Context | Function | Example | |---------|----------|---------| | HTML body | esc_html() | ` | | HTML attribute | escattr() | "> | | URL/href | escurl() | "> | | Textarea content | esctextarea() | | | Inline JS value | escjs() | onclick="alert('')" | | Rich HTML (post content) | wpksespost() | | | Custom allowed HTML | wpkses() | echo wpkses( $html, $allowed_tags );` |

Translation + escaping combos:

  • esc_html__() / esc_html_e() — translatable escaped strings
  • esc_attr__() / esc_attr_e() — translatable escaped attributes
  • wp_kses_post() on __() output for rich translated content

Input Sanitization

Sanitize all user input immediately upon receipt, before storage or processing:

| Data Type | Function | |-----------|----------| | Plain text | sanitize_text_field( wp_unslash( $_POST['field'] ) ) | | Textarea | sanitize_textarea_field( wp_unslash( $_POST['field'] ) ) | | Email | sanitize_email( $_POST['email'] ) | | Integer | absint( $_POST['id'] ) or intval( $_POST['num'] ) | | Filename | sanitize_file_name( $_FILES['file']['name'] ) | | HTML class | sanitize_html_class( $_POST['class'] ) | | Key/slug | sanitize_key( $_POST['key'] ) | | Title/slug | sanitize_title( $_POST['title'] ) | | URL | esc_url_raw( $_POST['url'] ) (for storage — use esc_url() for display) |

Always wp_unslash() superglobals before sanitizing — WordPress adds slashes to $_GET, $_POST, $_REQUEST.

Nonce Verification

Every form submission and AJAX request must include a nonce for CSRF protection:

Forms

// In the form template:
wp_nonce_field( 'myplugin_save_action', 'myplugin_nonce' );

// In the handler:
if ( ! isset( $_POST['myplugin_nonce'] ) ||
     ! wp_verify_nonce( sanitize_text_field( wp_unslash( $_POST['myplugin_nonce'] ) ), 'myplugin_save_action' ) ) {
    wp_die( esc_html__( 'Security check failed.', 'myplugin' ) );
}

AJAX

// Enqueue with nonce:
wp_localize_script( 'myplugin-script', 'myPluginAjax', array(
    'nonce' => wp_create_nonce( 'myplugin_ajax_nonce' ),
    'url'   => admin_url( 'admin-ajax.php' ),
) );

// In the AJAX handler:
check_ajax_referer( 'myplugin_ajax_nonce', 'nonce' );

Admin pages

check_admin_referer( 'myplugin_settings_action', 'myplugin_settings_nonce' );

Capability Checks

Always verify the current user has permission before performing privileged operations:

// Before saving settings:
if ( ! current_user_can( 'manage_options' ) ) {
    wp_die( esc_html__( 'Unauthorized.', 'myplugin' ) );
}

// Before editing posts:
if ( ! current_user_can( 'edit_post', $post_id ) ) {
    wp_die( esc_html__( 'Unauthorized.', 'myplugin' ) );
}

Common capabilities: manage_options, edit_posts, publish_posts, edit_others_posts, delete_posts, upload_files, manage_categories, edit_users.

Database Security

Never pass unsanitized data into SQL. Always use $wpdb->prepare():

global $wpdb;

// Parameterized query:
$results = $wpdb->get_results(
    $wpdb->prepare(
        "SELECT * FROM {$wpdb->prefix}custom_table WHERE user_id = %d AND status = %s",
        $user_id,
        $status
    )
);

// Prefer CRUD methods for single-row operations:
$wpdb->insert( $wpdb->prefix . 'custom_table', array(
    'user_id' => $user_id,
    'status'  => $status,
), array( '%d', '%s' ) );

$wpdb->update( $wpdb->prefix . 'custom_table',
    array( 'status' => 'active' ),
    array( 'id' => $row_id ),
    array( '%s' ),
    array( '%d' )
);

$wpdb->delete( $wpdb->prefix . 'custom_table',
    array( 'id' => $row_id ),
    array( '%d' )
);

File Operations

Use the WP_Filesystem API instead of direct PHP file functions:

global $wp_filesystem;
WP_Filesystem();

$wp_filesystem->put_contents( $file_path, $content, FS_CHMOD_FILE );
$content = $wp_filesystem->get_contents( $file_path );

For uploads, use wp_handle_upload():

$uploaded = wp_handle_upload( $_FILES['myfile'], array( 'test_form' => false ) );
if ( isset( $uploaded['error'] ) ) {
    wp_die( esc_html( $uploaded['error'] ) );
}

AJAX & REST Security

AJAX handlers

add_action( 'wp_ajax_myplugin_action', 'myplugin_ajax_handler' );

function myplugin_ajax_handler(): void {
    check_ajax_referer( 'myplugin_nonce', 'nonce' );

    if ( ! current_user_can( 'edit_posts' ) ) {
        wp_send_json_error( 'Unauthorized', 403 );
    }

    $data = sanitize_text_field( wp_unslash( $_POST['data'] ) );
    // ... process ...

    wp_send_json_success( array( 'result' => $data ) );
}

REST endpoints

register_rest_route( 'myplugin/v1', '/items', array(
    'methods'             => 'GET',
    'callback'            => 'myplugin_get_items',
    'permission_callback' => function (): bool {
        return current_user_can( 'read' );
    },
) );

Never set permission_callback to __return_true unless the endpoint is intentionally public.

Redirects & JSON Responses

// Safe redirect (restricts to allowed hosts):
wp_safe_redirect( admin_url( 'admin.php?page=myplugin' ) );
exit;

// JSON responses:
wp_send_json_success( $data );
wp_send_json_error( $message, $status_code );

// Terminate execution properly:
wp_die( $message, $title, array( 'response' => 403 ) );

For the full function reference with signatures and examples, see references/security-functions.md.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.