Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Basic WordPress hardening #709

Merged
merged 4 commits into from
Jul 1, 2021
Merged

Basic WordPress hardening #709

merged 4 commits into from
Jul 1, 2021

Conversation

gregrickaby
Copy link
Contributor

@gregrickaby gregrickaby commented Jun 30, 2021

Closes N/A

DESCRIPTION

One of our clients was recently put through a security audit and I had to make some updates in order to make them compliant. I'm simply bringing these updates back to wd_s.

  • Remove generator meta tags
  • Disable XML RPC
  • Change default REST-API headers from null to *

Note: this PR is not an exhaustive list of ways to secure WordPress, but rather a starting point... so we can provide our future clients peace of mind.

SCREENSHOTS

screenshot

STEPS TO VERIFY

  1. gh pr checkout 709
  2. View the front-end and look for generator tags
  3. Inspect any REST-API endpoint and verify the Access-Control-Allow-Origin is set to *

@gregrickaby gregrickaby marked this pull request as ready for review June 30, 2021 17:45
@gregrickaby gregrickaby changed the title WordPress hardening Basic WordPress hardening Jun 30, 2021
@gregrickaby gregrickaby merged commit 2fd5d57 into main Jul 1, 2021
@gregrickaby gregrickaby deleted the feature/secure-headers branch July 1, 2021 18:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant