If evidence of compromise appears, follow the incident response checklist below.

Incident response checklist (if compromise suspected)

1. Isolate and contain: Temporarily take the site offline or restrict admin access to known-safe IPs.
2. Invalidate sessions: Force logout all users and reset admin passwords.
3. Preserve logs and backups: Collect application and server logs; create an image or frozen backup for forensic analysis.
4. Assess scope: Identify compromised accounts, altered files, and changed database records.
5. Remove persistent backdoors: Replace modified files with known-clean copies from trusted backups or repositories.
6. Patch and harden: Remove or patch the vulnerable plugin and update WordPress core, themes, and other plugins.
7. Rebuild if necessary: For deep compromises, rebuild on a fresh instance and restore only verified-clean data.
8. Monitor: Keep elevated monitoring for at least 30–90 days for signs of reinfection or residual artefacts.
9. Notify stakeholders: Inform affected users or stakeholders and comply with applicable disclosure and regulatory obligations.

Developer guidance — permanent fixes

Plugin and theme authors should address the root cause using these secure development practices:

• Input validation and sanitation: Do not store arbitrary HTML. For plain text, use sanitize_text_field() or wp_strip_all_tags(). For limited HTML, use wp_kses() with a strict allowlist.
• Escape on output: Always escape when rendering: use esc_html(), esc_attr(), esc_js(), or context-appropriate functions.
• Capability checks and nonces: Verify appropriate capabilities (e.g., current_user_can('manage_options')) and use nonces (wp_nonce_field() and check_admin_referer()).
• Avoid echoing user data into JavaScript: Use wp_json_encode() and escape for JS contexts.
• Use prepared statements: Use $wpdb->prepare() for SQL operations.
• Audit output contexts: Treat each output location (HTML body, attribute, JS string, URL) with the appropriate escaping.
• Security testing: Add tests and code-review checklists that validate sanitization and escaping.

Example conceptual fix:

// On input:
$clean_message = sanitize_text_field( wp_kses( $_POST['ohmem-message'] ?? '', $allowed_tags ) );
update_option( 'my_plugin_ohmem', $clean_message );

// On output:
echo esc_html( get_option( 'my_plugin_ohmem' ) );

Long-term hardening recommendations for site owners

• Reduce the number of admin accounts to minimize attack surface.
• Apply least privilege: restrict accounts to necessary capabilities.
• Require 2FA for privileged accounts and encourage it for editorial users.
• Keep WordPress core, themes, and plugins updated; remove unused components.
• Maintain regular, secure off-site backups.
• Consider implementing a Content Security Policy (CSP) for admin pages to reduce XSS impact — test carefully to avoid breaking admin UI.
• Use monitoring and file-integrity checks to detect unauthorized changes.

Example search queries and scans (safe, non-exploitative)

Use these detection-oriented SQL queries to search for suspicious stored content. Back up the database before modifying or deleting any records.

-- Search for 
			
				
			
					

							
			
			
			





		

		
					
				 
 
   
 
  
 
 查看我的訂單
 0 
 
 
  
 
 
  
 
 
 
 小計
 
稅金和運費在結帳時計算
 
 
  
 
 
 
   結帳