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

apc: rework sanitization to not use WP functions (#240) #241

Merged
merged 1 commit into from
Oct 27, 2021

Conversation

stklcode
Copy link
Contributor

fixes #240

WordPress is not initialized when the APC proxy is called, so we must not rely on logic like wp_unslash().

Use filter_input to sanitize untrusted data and drop the unslashing, as it is not necessary in this place.

WordPress is not initialized when the APC proxy is called, so we must
not rely on logic like wp_unslash().

Use filter_input to sanitize untrusted data and drop the unslashing, as
it is not necessary in this place.
@stklcode stklcode added the bug label Aug 15, 2021
@stklcode stklcode added this to the 2.3.2 milestone Aug 15, 2021
Copy link
Member

@pfefferle pfefferle left a comment

Choose a reason for hiding this comment

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

LGTM

@stklcode stklcode merged commit d2be235 into develop Oct 27, 2021
@stklcode stklcode deleted the fix/240-apcproxy branch October 27, 2021 18:02
stklcode added a commit that referenced this pull request Oct 28, 2021
WordPress is not initialized when the APC proxy is called, so we must
not rely on logic like wp_unslash().

Use filter_input to sanitize untrusted data and drop the unslashing, as
it is not necessary in this place.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cachify is broken for APC with Apache with cachify 2.3.1
2 participants