Restrict access to options-*.php pages

A quick and dirty way of doing this is by adding a .htaccess file to the wp-admin directory, with the following content.

<FilesMatch "^options-(.*)\.php$">
  Order Allow,Deny
  Deny from all
</FilesMatch>

Related Posts:

  1. Settings API vs Theme Customizer
  2. Run function AFTER theme options are saved?
  3. Settings API – sanitizing urls, email addresses and text
  4. Add your own settings page for plugin
  5. Adding an html editor to plugin settings page
  6. add static page to reading settings for custom post type
  7. How to display an admin notice after updating plugin settings?
  8. Add settings fields on options discussion admin page
  9. Validate an option array
  10. Dynamic settings fields with Settings API
  11. Settings API repeater fields
  12. do_settings_sections() doesn’t escape quotes
  13. Import / Export Settings API fields values?
  14. Saving multiple checkboxes with WordPress settings api
  15. Letting user dynamically create fields using Settings API
  16. wordpress settings api add fields
  17. Adding labels to Setting titles with API
  18. register_setting sanitize callback $input is null
  19. Can I dynamically create duplicate fields with the Settings API?
  20. What exactly is the purpose of settings_fields()?
  21. Persist fields with Setting API
  22. wordpress settings API and option array structure
  23. Echo all API Settings sections?
  24. Settings Page won’t save
  25. How do I save custom options on the options page ‘Reading’?
  26. Settings API – generating field value based on a different field?
  27. Submit options page input values with decimals
  28. Using multiple settings_fields() on 1 settings page
  29. Settings API store serialized data in the database (The Right Way)
  30. Output ‘do_settings_sections()’ as tabs, not one under the other
  31. Saving plugin’s settings in 1 field in json format
  32. PHP Notice: Undefined offset: 0 in /wordpress/wp-includes/plugin.php and Register Settings API change
  33. Hide output of add_settings_field()
  34. How to make new plugin setting checkbox default as checked
  35. How to wrap html around Settings API add_settings_section()
  36. What is the best way to save and retrieve Multiple rows of data with the Settings API?
  37. Storing HTML in wp_options
  38. Multiple fields with add_settings_field callback
  39. Settings API: Two update notices after saving settings?
  40. Settings API in Section
  41. Storage of array in settings
  42. Settings API and dynamically generated submenu pages
  43. Error: options page not found when I try to save the changes made in my settings page
  44. Display Each Setting Section In Each Specific Tab within Same Page || Settings API
  45. WordPress Settings API – Sanitize Integer
  46. Preserve old values on error in setting API
  47. WordPress API Setting : the title of the section rendered not showing
  48. add_settings_section() order
  49. Splitting do_settings_sections within HTML?
  50. Why are these settings unregistered?
  51. Settings field is not showing up in the general options page
  52. How to use/retrieve an options array, with defaults, using get_option()
  53. How to prevent options.php deleting valid existing data from the database
  54. Displaying errors with settings api
  55. Displaying validation message in options-general.php
  56. How I can Make two input field at add_settings_section
  57. Settings Page – Option won’t save in database
  58. Customize format of settings
  59. Seeking clarity on data sanitization fields for settings textarea
  60. How to create a WordPress options page
  61. When should I use register_setting() and add_settings_field()
  62. Why aren’t these WordPress options being saved to the database correctly?
  63. input on custom settings page adds http://
  64. Is it possible to get a list of options for a specific options group?
  65. update_option_$option action not working as expected
  66. Saving array of data to database using wordpress settings API
  67. settings api sub menu and data not populating
  68. how to get wp_editor to save data in plugin admin page
  69. Getting all the settings for a plugin
  70. Can someone tell me where I’ve gone wrong with this plugin’s Settings page?
  71. Use the Settings API to whitelist a setting, but don’t output it
  72. How to handle complex data with Settings API
  73. Can’t save settings to database using Setting API
  74. Verify Submitted Form Values and Show Warning Messages with Setting API
  75. WordPress settings API VS Table In Database?
  76. settings api and the data passed in the parameter
  77. Writing Mysql and Php code in wordpress Posts
  78. Should I escape the html for the settings field created with add_settings_field?
  79. How to Save value from two inputs as array?
  80. Assign value to custom checkbox using get_option()
  81. Multiple plugins linked to same settings page
  82. Settings page – can’t change checkbox to unchecked
  83. Add Logo Upload per Setting API
  84. Add two input fields in add_settings_field
  85. Custom setting field value not working inside add_action init hook
  86. settings api callback functions won’t display?
  87. How to move setting field up a row on general page?
  88. Option doesn’t save
  89. Save button in theme customization page stays disabled
  90. Settings API Multiple Checkbox in General Settings
  91. Settings api sanatize callback not being triggered
  92. Can I use add_option for a plugin categories and how?
  93. Adding Form Fields with Settings API
  94. Custom button and html with [settings api plugin]
  95. illegal offset in option add
  96. WordPress’s automatic ‘Settings saved.’ text fails to display after tapping on the ‘Save Changes’ button on my custom settings page
  97. Tab Nav and WordPress Settings API
  98. Do I need to validate the nonce when using the settings api?
  99. How to sanitize settings API value
  100. Hide block of HTML if the users role is a certain role