Changeset 43287 for branches/4.9/src/wp-includes/capabilities.php

Timestamp:

05/15/2018 08:58:05 PM (7 years ago)

Author:

iandunn

Message:

Privacy: Require manage_privacy_options to edit policy page.

A user is required to have the manage_privacy_options capability in order to determine which page is set as the privacy policy (the wp_page_for_privacy_policy). Given that, it doesn't make sense to allow users without that capability to edit or delete the page.

A similar situation exists with the page_for_posts and page_on_front options, but Editors are allowed to edit those pages. The reason that this situation is different is because it is more likely that an administrator will want to restrict modifications to the privacy policy, than it is that they will want to allow modifications. Modifications to the policy often require specialized knowledge of local laws, and can have implications for compliance with those laws.

Props dlh, desrosj.
Merges [43286] to the 4.9 branch.
Fixes #44079.

Location:

branches/4.9

Files:

• . (modified) (1 prop)
• src/wp-includes/capabilities.php (modified) (2 diffs)

branches/4.9/src/wp-includes/capabilities.php

@@ -120 +120 @@
             }
         }
+
+        /*
+         * Setting the privacy policy page requires `manage_privacy_options`,
+         * so deleting it should require that too.
+         */
+        if ( (int) get_option( 'wp_page_for_privacy_policy' ) === $post->ID ) {
+            $caps = array_merge( $caps, map_meta_cap( 'manage_privacy_options', $user_id ) );
+        }
+
         break;
         // edit_post breaks down to edit_posts, edit_published_posts, or
@@ -181 +190 @@
             }
         }
+
+        /*
+         * Setting the privacy policy page requires `manage_privacy_options`,
+         * so editing it should require that too.
+         */
+        if ( (int) get_option( 'wp_page_for_privacy_policy' ) === $post->ID ) {
+            $caps = array_merge( $caps, map_meta_cap( 'manage_privacy_options', $user_id ) );
+        }
+
         break;
     case 'read_post':