Automattic / Automattic/jetpack
General: make sure Jetpack can't be executed outside of WordPress
- Dominant language
- PHP
- Stars
- 1.8k
- Forks
- 898
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 774
Description
See https://codex.wordpress.org/Writing_a_Plugin#Plugin_Files
> Security Note: Consider blocking direct access to your plugin PHP files by adding the following line at the top of each of them, or be sure to refrain from executing sensitive standalone PHP code before calling any WordPress functions.
`defined( 'ABSPATH' ) or die( 'No script kiddies please!' );`
Suggested here:
https://wordpress.org/support/topic/periodic-fatal-error?replies=11&view=all#post-7691891
Contributor guide
Research direction
No repository files or tests are named. Start by locating Jetpack’s plugin PHP entry points and reviewing the linked WordPress plugin guidance; done means sensitive plugin code cannot execute when loaded directly outside WordPress.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100