Requirements and responsibilities
Have named ownership of the domain, selected xCloud team and site, and WordPress administrator access. For this scenario, agree who supplies the data and signs off: A maintainer receives a version-based finding for a production plugin.
xCloud agent capability boundaries · WordPress roles and capabilities
Use a compatible Nginx or OpenLiteSpeed stack for native WordPress. Verify current server resources, plan eligibility and each selected plugin or service license and requirements before installing; a Docker server does not host a new native WordPress site.
xCloud agent capability boundaries · WordPress plugin administration
Prepare a safe test identity and a completed, accessible backup before consequential changes. The important failure to plan around is: A finding can persist after a partial update; virtual patching does not update code.
Before a source copy or backup restore starts, the authorized operator must restrict the target and quarantine outbound mail, payment, fulfillment and other provider effects at the receiving environment. Restored WordPress settings can overwrite plugin suppression; reapply sandbox credentials and verify isolation before tests.
Create a staging environment in xCloud · Site backups in xCloud
Illustrative situation
Illustrative scenario, not a customer case study: A maintainer receives a version-based finding for a production plugin. The affected version is replaced or an approved mitigation is documented and rescanned.
Choose the approach
Choose remediation from the vendor advisory and compatibility evidence, not severity alone. Verify the selected provider or plugin documentation and license against this requirement; xCloud hosting does not supply its business configuration.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · WordPress roles and capabilities · Manage WordPress updates with Updates Manager
Keep application setup, domain/DNS ownership, mail delivery and external integrations with their named administrators. Use a plain documented path when a proposed integration cannot be demonstrated end to end.
xCloud agent capability boundaries · WordPress plugin administration
Dashboard and application procedure
Follow these steps yourself, or use the scoped AI handoff below for supported hosting operations.
Step 1 of 5
Identify the affected version
- Where
- xCloud Vulnerability Checker
- Permissions
- Named xCloud team/site administrator; confirm the exact production or staging target.
- Inputs
- Owner, hostname, approved requirements, sample record and decision date. Identify the affected version.
- Action
- Open the xCloud finding for the exact site and record plugin slug, installed version, advisory and time. Confirm whether the component is active or exposed in the site's workflow.
- Expected result
- The team has a specific affected component, not a generic risk label.
- Verify
- Match the installed version to the advisory's affected range.
- If it fails
- If identity or version cannot be confirmed, avoid a speculative update and investigate first.
Sources: Vulnerability Checker in xCloud · xCloud agent capability boundaries
Step 2 of 5
Choose an evidence-backed fix
- Where
- WordPress administrator or the selected plugin/application
- Permissions
- Named WordPress or selected app administrator; business owner approves results.
- Inputs
- Target team/site, server or plugin version, license and documented prerequisites. Choose an evidence-backed fix.
- Action
- Read the vendor fix notes and dependencies. Compare update, disable, removal and paid Site Security PRO as distinct options; note that virtual patching does not replace vulnerable code.
- Expected result
- The owner has a justified remediation choice.
- Verify
- Record fixed version availability, compatible PHP/WordPress range and any licensing dependency.
- If it fails
- If no fix exists, choose an interim exposure reduction with an explicit review deadline.
Sources: WordPress roles and capabilities · WordPress plugin administration · Site Security PRO setup and eligibility · Vulnerability Checker in xCloud
Step 3 of 5
Test selected fix on staging
- Where
- xCloud production and staging dashboards
- Permissions
- Named xCloud team/site administrator; confirm the exact production or staging target.
- Inputs
- Approved change scope, backup state, selected version and maintenance window. Test selected fix on staging.
- Action
- Confirm a completed backup and use eligible xCloud staging from the dashboard. Apply the selected plugin update or removal to staging and record exact version change.
- Expected result
- A test environment contains the proposed remediation.
- Verify
- Check plugin state and staging deployment log; run a login and the site's important function.
- If it fails
- If staging breaks, keep production unchanged and seek a vendor-supported alternative.
Sources: Create a staging environment in xCloud · xCloud agent capability boundaries
Step 4 of 5
Apply and test production change
- Where
- xCloud Updates Manager and WordPress administrator
- Permissions
- Named xCloud team/site administrator; confirm the exact production or staging target.
- Inputs
- Test accounts, sample content or transaction, expected result and provider access. Apply and test production change.
- Action
- Approve the exact production plugin change, apply only that selection and wait for completion. Test the site's form, checkout, membership or booking path that uses the plugin.
- Expected result
- The site works with the intended component version.
- Verify
- Compare live version, visible flow and application record against the pre-change sheet.
- If it fails
- If a business flow fails, start the agreed recovery path without blindly restoring over newer records.
Sources: Manage WordPress updates with Updates Manager · Manage WordPress core, themes and plugins
Step 5 of 5
Rescan and close the finding
- Where
- xCloud Vulnerability Checker
- Permissions
- Named xCloud team/site administrator; confirm the exact production or staging target.
- Inputs
- Observed results, unresolved failures, backup point and owner contacts. Rescan and close the finding.
- Action
- Run a fresh vulnerability scan when the connected capability supports it and record remaining findings. Share the result and unresolved risk with the owner.
- Expected result
- Closure has version, functionality and scan evidence.
- Verify
- Compare original and new finding IDs and verify that the component version changed as intended.
- If it fails
- If the finding persists, investigate scanner freshness or incomplete update instead of marking it resolved.
Sources: Vulnerability Checker in xCloud · xCloud agent capability boundaries
Maintenance
Assign a cadence for selected WordPress core, theme and plugin updates, review version-based findings and retest the path in this guide. In particular, repeat: The affected version is replaced or an approved mitigation is documented and rescanned. A chat prompt is not a scheduled task.
Manage WordPress updates with Updates Manager · Vulnerability Checker in xCloud
Record actual backup completion, storage access and responsible staff. Recheck connected application and provider behavior after changes rather than relying on a site health status alone.
Recovery decisions
Before restoring, compare the chosen recovery point with newer business records. A finding can persist after a partial update; virtual patching does not update code. Use the xCloud dashboard for native restore only after the owner approves target and scope; reconcile or preserve newer data first.
Validate the restored copy with representative content, authentication, HTTPS and this guide’s business acceptance test before moving traffic or closing the incident.
AI handoff
Connect xCloud MCP through the current documented profile and grant only the scopes needed for the selected team. Discover tool schemas first. Read resources to plan; require approval for any supported write. Use returned dashboard URLs for manual work. The packaged REST wrapper accepts GET requests only.
Supported scope
- Confirm requirements and inspect resources mcp · read
Discover the connected profile and operation schema first; only teams granted to the connection are visible.
Checkpoint: Confirm exact team, server and site identity. Use dashboard_url returned by the resource; do not invent a dashboard link.
Operation identifiers and scopes to discover
teams.index, servers.show, sites.show
Scopes: read:servers, read:sites
xCloud MCP documentation and connection profiles · xCloud agent capability boundaries
- Inspect and rescan vulnerabilities mcp · write
Discover the rescan tool in the connected profile; triggering a scan is a write. Findings describe known version vulnerabilities, not proof of complete site safety.
Checkpoint: Read findings before proposing remediation. Approve a rescan and verify its completion; never silently ignore a finding.
- Configure WordPress content, users and selected plugins app · manual
Requires a named WordPress administrator or suitable editor. Plugin behavior, commercial license, payment, email and external integration are verified in the chosen vendor documentation and application; xCloud hosting or MCP reads do not configure them.
Checkpoint: Open the actual WordPress or selected plugin interface, record the version and role, and have the business owner accept a real user journey.
WordPress roles and capabilities · WordPress plugin administration
- Create and synchronize WordPress staging dashboard · manual
WordPress staging requires an eligible paid plan. The API staging-create operation is for Git sites.
Checkpoint: Use Site overview → Add Staging and staging Site → Manage Staging. Inspect push/pull scope before overwriting data.
- Review and apply selected WordPress updates mcp · write
Discover the current schema. Identify explicit plugin/theme slugs and update type; do not omit selection and unintentionally update all items.
Checkpoint: Approve selected changes only after a completed backup and staging checks. Verify asynchronous completion and business flows.
Operation identifiers and scopes to discover
sites.wordpress.update
Scopes: read:sites, write:sites
WordPress plugin and theme operations · Manage WordPress updates with Updates Manager
Copyable agent brief
Manual checkpoints
- The named WordPress, app, dashboard or provider administrator performs the guide’s actual configuration step: Confirm a completed backup and use eligible xCloud staging from the dashboard. Apply the selected plugin update or removal to staging and record exact version change.
- The business owner compares the controlled sample with this observable result: The site works with the intended component version.
- Staging push/pull, native backup schedules, restores and cache-setting edits require the authorized xCloud dashboard operator; the packaged REST wrapper is GET-only.
Feature coverage
- business-acceptance (covered): The affected version is replaced or an approved mitigation is documented and rescanned. Apply and test production change
- recovery (covered): A finding can persist after a partial update; virtual patching does not update code. Rescan and close the finding
Sources
- xCloud agent capability boundaries
- WordPress roles and capabilities
- WordPress plugin administration
- Site backups in xCloud
- WordPress hardening handbook
- Create a staging environment in xCloud
- xCloud MCP documentation and connection profiles
- Manage WordPress updates with Updates Manager
- Vulnerability Checker in xCloud
- Site Security PRO setup and eligibility
- Manage WordPress core, themes and plugins
- Vulnerability operations
- WordPress plugin and theme operations