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

[CMS-859] Add theme vulnerability check #103

Merged
merged 16 commits into from
Aug 1, 2022

Conversation

kyletaylored
Copy link
Contributor

Even though we use WPScan (formerly WPVulnDB), we only made use of the plugin vulnerabilities and never the theme vulnerabilities. This PR adds in a new command for checking the themes, similar to how wp launchcheck plugins works.

There are also a few typos and grammar pieces that were fixed as well.

When this command runs on the platform, it does not explicitly utilize the --all flag, but that’s because the plugin command (which does have an option for --all) does not actually implement this logic - it will pull all plugins and makes no distinction whether they’re active or not.

This commit will just assume that when anyone (including the platform) runs the “all” command, it will expect the --all flag is enabled.
@danielbachhuber
Copy link
Contributor

Thanks @kyletaylored !

@greg-1-anderson Up for building this into the Phar when you have a moment?

When this command runs on the platform, it does not explicitly utilize the --all flag, but that’s because the plugin command (which does have an option for --all) does not actually implement this logic - it will pull all plugins and makes no distinction whether they’re active or not.

This commit will just assume that when anyone (including the platform) runs the “all” command, it will expect the --all flag is enabled.
…heck into add-theme-check

# Conflicts:
#	.travis.yml
@ccharlton
Copy link
Contributor

Build reports:

  1. Two instances of "Error: Error establishing a database connection"
  2. One instance of of "Error: The 'twentyfifteen' theme could not be found."

@kyletaylored
Copy link
Contributor Author

@danielbachhuber I had committed a lot here, some of it to try and get successful tests to run on TravisCI, so I went ahead and started a TravisCI to Github Actions migration (#107) which should probably get merged first, then we can start adding in these updates. What do you think @greg-1-anderson?

@greg-1-anderson
Copy link
Member

Yeah, looks good to me. Let's rebase this against #107 after that PR is merged.

@kyletaylored kyletaylored changed the title Add theme vulnerability check [CMS-320] Add theme vulnerability check Oct 8, 2021
@kyletaylored kyletaylored requested a review from a team as a code owner March 23, 2022 15:46
Copy link
Contributor

@jazzsequence jazzsequence left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This LGTM. I've tested locally using wp --require=wp-cli/wp_launch_check/vendor/autoload.php launchcheck themes and it works as expected. Looks like it's been updated with the main branch, as well, so this should be g2g.

@jazzsequence jazzsequence merged commit ccd1129 into pantheon-systems:main Aug 1, 2022
@CdrMarks CdrMarks changed the title [CMS-320] Add theme vulnerability check [CMS-859] Add theme vulnerability check Aug 5, 2022
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.

5 participants