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.

Sign up for GitHub

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

Jump to bottom

Adds WP.Security.SafeRedirect documentation. #1826

Merged
merged 1 commit into from Nov 7, 2019
Merged

Adds WP.Security.SafeRedirect documentation. #1826

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
19 changes: 19 additions & 0 deletions WordPress/Docs/Security/SafeRedirectStandard.xml
View file
Open in desktop
@@ -0,0 +1,19 @@
<documentation title="Safe Redirect">
<standard>
<![CDATA[
wp_safe_redirect() should be used whenever possible to prevent open redirect vulnerabilities. One of the main uses of an open redirect vulnerability is to make phishing attacks more credible. In this case the user sees your (trusted) domain and might get redirected to an attacker controlled website aimed at stealing private information.
]]>
</standard>
<code_comparison>
<code title="Valid: Redirect can only go to allowed domains.">
<![CDATA[
<em>wp_safe_redirect</em>( $location );
]]>
</code>
<code title="Invalid: Unsafe redirect, can be abused.">
<![CDATA[
<em>wp_redirect</em>( $location );
]]>
</code>
</code_comparison>
</documentation>