WordPress Security Cleanup, Page Creation & Review

What this case study is based on

Completed Upwork engagement supplied by Xequent. Only what the project record actually shows is stated here. Where no measurable outcome was recorded, none is claimed.

The security problem

• The project required security cleanup alongside site content/page work.
• Security corrections had to be made without losing sight of the website's normal publishing needs.
• The client wanted the issue addressed within an agreed timeframe.

Technical approach

The specific controls follow from the site's architecture and its observed traffic, never from a template. The workflow below is the reasoning behind the work, described at the level the project record supports.

1. Assess the affected WordPress installation before removing or changing files.
2. Check core, plugin and theme components for indicators of compromise or unsafe configuration.
3. Review administrative access and security-sensitive settings.
4. After cleanup, review the affected pages and confirm the site remains usable.

Result and client evidence

• The client gave a 5.0/5 rating.
• The written feedback states that the website security issues were resolved within the promised timeline and expresses interest in future work.

Detection and remediation are different jobs

A scan tells you what is recognisable. It does not establish how far an attacker moved, remove the persistence mechanisms left behind, or close the path they came in through. That is why a scan result is where an engagement starts, not where it ends.

On a compromised site the sequence that works is preserve evidence, contain, investigate, clean files and database, hunt persistence, then find the entry point. Skipping that last step is why sites get reinfected within a week of a cleanup that looked complete. The malware removal service covers the full sequence, and hardening is what changes the outcome next time.