Installed-package-aware core checks
Changing the WordPress administration language should not suddenly make legitimate core files look modified.
Trusted-source comparison
Know what changed—and repair only when the source is truly trusted.
Nexus compares WordPress core and eligible components against trusted sources, identifies unexpected changes and uses verification-first repair workflows rather than overwriting files blindly.
Official core checksumsPackage-aware localeVerify before replaceRollback safeguards
INTEGRITY ENGINESOURCE VERIFIED
WordPress coreOfficial checksums matched
Core fileUnexpected modification needs review
Repair candidateVerified before publication
Official source verification
Nexus resolves the correct official package for the installed WordPress core package rather than guessing from the current UI language.
Verification-first repair
A replacement candidate is verified before the live file is touched, with rollback protection if final verification fails.
Trust is evidence
Integrity is more than comparing a version number.
Running files can change after installation, and the current administration language is not always the language of the installed core package. Nexus keeps source identity and repair safety tied to the actual package being verified.
- Official WordPress core checksum comparison
- Installed core package locale awareness
- Exact official localized package resolution
- Candidate verification before live replacement
- Restore point and rollback safeguards
- Plugin and theme comparison where a suitable trusted source exists
Capability map
A repair path designed around source provenance.
Integrity gives the scanner and Rescue Center structural evidence while keeping recovery conservative.
Core integrity
Compare the installed WordPress core against the correct official checksum set and identify modified, missing or unexpected files.
- Package-locale aware
- Official checksums
- No UI-language false positives
Trusted package resolution
Resolve the exact official package suitable for verification and repair rather than guessing a localized download URL.
- Official WordPress source
- HTTPS package validation
- Safe fallback rules
Changed-file prioritization
Use integrity differences to focus investigation without pretending every modification is malware.
- Unexpected files
- Modified files
- Scanner connection
Verify, repair, verify again
Verify the clean candidate, preserve the old state, publish the replacement and verify the live copy—with automatic rollback if the final check fails.
- Pre-publish verification
- Restore point
- Post-copy verification
Operational flow
Trusted source first. Live-file change last.
A repair is allowed only when Nexus can prove what the correct file should be.
Identify
Determine the installed core package and the trusted official source.
Compare
Evaluate current hashes and package structure.
Verify candidate
Download and verify the replacement before changing the live site.
Repair safely
Preserve the previous state, replace, verify again and roll back automatically on failure.
Make repair conservative and reversible.
- Use the installed package locale
- Verify official packages before publishing files
- Preserve the previous state
- Rollback if final verification fails
Guess what the clean file should be.
- Use the current admin language as proof of the installed package
- Guess localized package URLs
- Overwrite custom code from an unrelated repository
- Leave a failed replacement live after verification failure
Feature questions
What buyers usually want to know.
Can changing the WordPress admin language create a false core warning?
It should not. Nexus derives core verification from the installed WordPress package rather than treating the current administration language as proof of which core package is installed.
Can Nexus repair localized WordPress installations?
Yes when the matching official package can be resolved safely. Nexus does not guess localized package URLs when the source cannot be verified.
What happens if a replacement file fails verification?
The candidate is checked before publication. If the final live-file verification still fails, Nexus restores the previous state automatically.
Does a clean integrity result guarantee the whole site is clean?
No. Database persistence, credentials, custom code and malicious configuration can exist even when official packages match. Integrity is one layer of Nexus.
Lumiverse Nexus PRO
Repair only when Nexus can prove what clean should look like.
WordPress integrity and controlled repair are part of Nexus PRO.