LTD is back · Limited time only

How to Disallow File Modifications in WordPress

Last updated on July 24, 2026

Key Takeaways

• Two related toggles: Disallow All File Modifications and Disallow Plugin/Theme Editor

• Prevents admins from editing code via the dashboard

• Protection against compromised admin accounts

• Doesn’t affect FTP/SSH access (only admin-based edits)

• Use the `DISALLOW_FILE_EDIT` constant for permanent protection

What Is the Disallow File Modifications feature?

By default, WordPress admin users can edit theme and plugin files via the dashboard:

  • Theme Editor: Appearance > Theme File Editor
  • Plugin Editor: Plugins > Plugin File Editor

This is a convenience feature for developers but creates a security risk. A compromised admin account can use the file editor to inject malicious code.

The Disallow File Modifications feature disables these editors. The site can still be updated via WP-CLI, FTP, SSH, or Git.

Why You Need It

The file editors are a high-value attack surface:

  • No version control: Direct file edits are not tracked
  • No code review: Changes can be made without oversight
  • No backup integration: Edits bypass most backup systems
  • Common malware vector: Compromised admin accounts use the file editor to inject backdoors

For production sites, the file editors should always be disabled.

How to Disallow File Modifications in WordPress

Step 1: Navigate to Settings

Click into the Classic Monks plugin settings in your WordPress dashboard.

Step 2: Go to the Security Tab

Click on the Security menu, then click the WP Protection subtab.

Step 3: Enable Disallow All File Modifications

Scroll to Disable all changes to all files via admin area and toggle on. This is the master toggle that disables all file modifications via the admin (including the plugin/theme editor AND plugin/theme updates from the admin).

Step 4: (Optional) Enable Disallow Plugin/Theme Editor

If you want to allow plugin/theme updates but still disable the editor, toggle on Disable file changes via plugin and theme editors (separate toggle). The admin can update plugins/themes from the Plugins page, but the editor is disabled.

Step 5: Save Changes

Click Save Changes.

Step 6: Test

Log in as an admin. Go to Appearance > Theme File Editor. The menu item should be missing (or show a “you don’t have permission” message). The same for Plugins > Plugin File Editor.

Configuration Options

Option Description Default
Disable all changes to all files via admin area Master toggle (disables all file changes via admin). Off
Disable file changes via plugin and theme editors Disable the editor only (allows updates). Off

The first toggle is the most restrictive. The second toggle is less restrictive (allows updates but not direct file editing).

What Gets Affected

  • The Theme Editor: disabled
  • The Plugin Editor: disabled
  • The plugin/theme update flow: disabled (only with the first toggle)
  • The admin’s ability to edit code via the dashboard: removed

What Does NOT Get Affected

  • FTP/SSH access: not affected (admins can still edit files directly)
  • The wp-cli: not affected (can be used to update plugins/themes)
  • The plugin/theme update via the WP-CLI: not affected
  • The custom code via Code Manager: not affected (this is a separate feature)

Troubleshooting

The Theme Editor is still showing

Cause: The toggle is off, or a caching plugin is serving the old admin menu.
Fix: Verify the toggle is on. Clear the cache. The admin menu is generated server-side, so a cache may be serving the old menu.

I need to edit a file urgently but the editor is disabled

Cause: The protection is working as intended.
Fix: Use FTP, SSH, or the file manager in cPanel/Plesk. For emergency edits, the DISALLOW_FILE_EDIT constant in wp-config.php can be temporarily set to false.

Plugin updates are not working

Cause: The master toggle (Disallow All File Modifications) also disables updates.
Fix: Use the second toggle (Disallow Plugin/Theme Editor) instead, which allows updates but blocks direct file editing.

The Code Manager feature is not working

Cause: Code Manager is a separate feature that uses a different mechanism.
Fix: Code Manager should work regardless of these settings. If it’s not working, check the Code Manager settings.

A previous admin left code edits that need to be reviewed

Cause: The previous admin may have used the file editor.
Fix: Use Git or a code comparison tool to review the file changes. The Disable File Modifications feature prevents future edits, not past edits.

Sumit Your Ideas or Feature Requests

All submissions go through a manual review, so not every idea will be published. That said, the most upvoted ideas are given priority on our official roadmap.Please check if your idea already exists before submitting. If you find it, simply upvote it to help us prioritize it.