Start With Evidence
Compare users, file changes, redirects, search snippets, server logs, and recent plugin updates against the owner’s known activity. Capture the exact symptom before changing settings so the next person can see what was tested.
Problem
Signs Your WordPress Site May Be Hacked
Identify practical hacked-site warning signs such as unknown admins, redirects, spam pages, modified files, login spikes, and search-result warnings.
Problem
The site looks mostly normal, but there are signs that WordPress may have been modified without approval.
For: WordPress site owners, administrators, and agencies improving security posture.
Workflow
What to review
Fix The Owner
Preserve evidence, remove unauthorized access, restore or replace modified components, and strengthen login and update controls. Keep the change narrow, reversible, and tied to the layer that actually owns the problem.
WPlura Fit
Web Plura Security Center - Login Protection, Access Safety, and Cloud Policy can help organize the local review, evidence, or handoff path where the product documentation verifies that workflow. Free WordPress.org plugins should be the first step when the local workflow is enough.
WordPress SecuritySeverity: HighLast reviewed: 2026-09-16
Diagnosis
Symptoms, causes, checks, and fixes
Symptoms
- The site looks mostly normal, but there are signs that WordPress may have been modified without approval.
- The issue is visible during routine WordPress, WooCommerce, or client review work.
- Owners need a clear next step before changing plugins, settings, payment flows, or content.
Most Common Causes
- Compromise can start through weak credentials, vulnerable plugins, exposed files, or unauthorized admin sessions.
- Recent updates, configuration drift, cache/CDN behavior, plugin settings, or incomplete operational review can hide the owner of the issue.
- Teams may be relying on assumptions instead of order notes, logs, local diagnostics, public response checks, or documented handoff evidence.
How To Confirm The Cause
- Compare users, file changes, redirects, search snippets, server logs, and recent plugin updates against the owner’s known activity.
- Record the affected URL, user role, workflow, plugin, order, product, or report section before changing settings.
- Compare the current result with the expected WordPress or WooCommerce behavior and preserve useful screenshots or exportable evidence.
Fixes
- Preserve evidence, remove unauthorized access, restore or replace modified components, and strengthen login and update controls.
- Apply the smallest reversible fix first, then clear only the relevant cache or retry only the affected workflow.
- Use a local report, CSV export, support-safe summary, or checklist when a developer, host, client, or payment provider needs evidence.
How To Verify The Fix
- Repeat the same workflow that exposed the issue.
- Confirm the visible status, report, order, product, page, or email path now matches the expected result.
- Document the final owner and next monitoring step so the issue does not quietly return.
When To Contact Support
Escalate when the issue involves hosting/network controls, payment-provider account state, private customer data, destructive restore work, or a code-level failure that cannot be safely confirmed from wp-admin.
References
Official references
Continue