Connected site requests are verified
Remote agent requests use HMAC-signed authentication and freshness checks before CMDPress accepts site actions.
Security across the workflow
WordPress management security for connected sites
CMDPress protects account access, team permissions, stored connection data, remote site actions, and the work history around managed WordPress sites.
- No credit card required
- First site free forever
- $2.99 per extra site
Protection areas
Security is built into access, actions, and evidence
This public overview explains what CMDPress protects without publishing secrets, internal keys, or sensitive infrastructure details.
Sensitive connection values stay protected
Site secrets, integration tokens, and other sensitive stored values use application encryption.
Two-factor authentication is available
Users can protect account access with two-factor authentication and recovery codes.
Roles limit what each person can do
Team policies and role-aware permissions separate owners, managers, support staff, and clients.
Vulnerability findings reach the right site
Security scans surface affected WordPress core, plugins, and themes with severity and site context.
Activity and logs support investigation
Site history, site activity, alerts, logs, and backups help teams understand what happened and when.
Visible controls
Security is part of everyday site management
The product keeps risk, access, history, and recovery next to the WordPress sites your team manages.
FAQ
Security questions
Is it safe to connect WordPress sites to a management dashboard?
Yes, when the connection, stored secrets and user accounts are protected. In CMDPress, remote agent requests use HMAC-signed authentication and freshness checks before any site action is accepted. Site secrets and integration tokens use application encryption, users can turn on two-factor authentication with recovery codes, and team roles limit what each person can do.
What does WordPress management security cover in CMDPress?
It covers account access, team permissions, stored connection data, remote site actions and the work history around your sites. On the sites themselves, security scans surface affected WordPress core, plugins and themes with severity, along with risky settings and malware indicators. Activity, logs, alerts and backups help the team see what happened and when.
Who can use Magic Login on my sites?
Only workspace members whose role and site access allow it. Magic Login opens wp-admin for a connected site without typing the site password, and access follows workspace roles, so owners, managers, support staff and clients each reach only what their role permits. Two-factor authentication adds a second check on every CMDPress account that enables it.
Does the CMDPress agent plugin change my site’s front end?
No. The agent is a lightweight plugin with no front-end interface, so visitors see nothing new on the site. It receives remote actions from CMDPress, and each request is verified with HMAC-signed authentication and freshness checks before it is accepted. CMDPress does not host your site or install WordPress, so the site stays on your current host.
Can I request a security review of CMDPress?
Yes. Contact CMDPress through the contact page for security reviews, procurement questions, enterprise access needs and portfolios above 1,000 sites. The public security overview explains what CMDPress protects without publishing secrets, internal keys or sensitive infrastructure details. You can also inspect the product in the public demo, which uses sample data and blocks real site connections.
Security questions welcome
Bring your site requirements to the conversation
Contact CMDPress for procurement questions, security reviews, enterprise access needs, and site portfolios above 1,000 sites.