Skip to Content
Browse documentation

Review WordPress Security in UAPP

Inspect security status and checks, manage administrator sessions and passwords, configure WP-Admin protection and review supported Nginx controls.

Open the site's Security tab. Availability and safe changes depend on the verified site, supported templates and working PHP/WordPress.

Checks and changes

Read actions include status, core/plugin checks, debug/config checks and administrator listing. These are scoped checks, not a guarantee that the site is free of compromise.

Confirmed changes can enable/disable the WordPress file editor, control version exposure, rotate salts, fix debug exposure, revoke a selected administrator's sessions or change an administrator password.

Administrator actions target the selected numeric user ID. A new administrator password requires at least 12 characters, at most 4096 UTF-8 bytes and no control characters. Refresh the administrator list if the user no longer has the expected role.

Salt rotation/session revocation can sign users out. Confirm the intended effect and retain a working access method. Mutations require confirmation and are blocked in demo mode.

WP-Admin server protection

FieldMeaning
Enabled / methodIP only, Password only, IP or password, or IP and password.
Allowed IPsOne IPv4, IPv6 or CIDR network per line. No address is added automatically.
HTTP authentication username/passwordSeparate server-level authentication credentials where the mode requires them.
Replace custom protectionExplicit consent when taking over detected custom rules.
ConfirmationRequired before applying the policy.

IP or password permits either condition; IP and password requires both. Verify the client address the server receives and preserve an alternative access path before restricting access. This is separate from WordPress administrator credentials.

Unsupported templates, custom configuration, failed configuration tests or server reloads can prevent application. Follow rollback warnings; if previous configuration cannot be restored, ask the provider to inspect the servers before retrying.

Nginx protection controls

Where supported and permitted, controls include XML-RPC, hotlink/frame protection, scanner/bad-bot/referrer filtering, common exploit, SQL/file injection, symlink and Slowloris protection, plus HSTS. Slowloris requires valid configured header/body timeout limits, 1–20000. Enabling HSTS requires a currently valid HTTPS certificate.

Review compatibility before tightening protection

Protection can affect legitimate applications and administration. HSTS can persist in browsers; ensure dependable HTTPS before enabling it. A successful setting change is not a complete security assessment.

If a change applied but status refresh failed, refresh Security before issuing another change.