Security · Guide
How to Check If a WordPress Theme Is Safe
Short answer
Check a WordPress theme's safety on its WordPress.org page first: look at the last update date, the tested-up-to version, the review rating, and the number of active installs. Then run the Theme Check plugin, which runs the same automated tests WordPress.org uses for theme submissions. If the theme is premium or from another marketplace, check the vendor's changelog and support history before you pay.
Key takeaways
- Patchstack counted 11,334 new WordPress vulnerabilities in 2025, with 9% in themes, so themes deserve the same checks as plugins.
- A theme with no update for over a year may still work, but it can hide unpatched flaws.
- Theme Check runs the same automated tests WordPress.org uses for theme submissions.
- WordPress.org themes must be GPL-compatible, free of PHP errors, and hand-reviewed before listing.
- Never use a nulled theme, since it can hide backdoors that no scanner will warn you about.
What makes a WordPress theme unsafe?
A theme is unsafe when its code lets an attacker run actions on your site, inject scripts, or read data it should not reach.
Themes run with full access to your site, so a flaw in a theme is as serious as a flaw in a plugin. Patchstack counted 11,334 new vulnerabilities across WordPress in 2025, up 42% on 2024, with 9% found in themes (Patchstack).
The risk is not only the flaw itself. Patchstack also found that 46% of disclosed vulnerabilities had no fix from the developer at the time of public disclosure (Patchstack). A theme whose author has stopped fixing flaws stays open even after the flaw is public.
Unsafe themes usually share a pattern: no updates for a long time, code copied from unknown sources, or extra features that belong in a plugin. Learn the common patterns in our guide to the most common WordPress vulnerabilities.
Where should you get a theme?
Get themes from WordPress.org, the theme author's own site, or a marketplace with a public changelog and support history.
WordPress.org lists only themes that pass its review. Every theme submitted there is hand-reviewed by a team of experts, and the automated Theme Check tool runs the same tests reviewers use (Theme Check).
Avoid free download sites that offer paid themes for nothing. Those copies are often changed to include hidden code, and you get no updates or support. Read why in our guide on whether nulled WordPress plugins are safe, since the same risks apply to themes.
Free and paid themes both need the same checks. A price tag does not prove a theme is safe, and a free theme from WordPress.org can be safer than a paid theme from an unknown seller. Compare the trade-offs in our guide to free vs premium WordPress themes.
How do you check a theme on WordPress.org?
Open the theme page on WordPress.org and check its last update, tested-up-to version, rating, and active installs before you install it.
Start with the update date. A theme updated in the last few months is being maintained, while one untouched for over a year may hide unpatched flaws. Check the “Tested up to” version too, and make sure it matches a recent WordPress release.
| Check | Where to see it | What it tells you |
|---|---|---|
| Last update | Theme page on WordPress.org | Whether the author still maintains it |
| Tested up to | Theme page on WordPress.org | Which WordPress version it supports |
| Reviews | Theme page, reviews tab | Repeat complaints and author replies |
| Changelog | Theme page or vendor site | Whether security fixes arrive promptly |
| Active installs | Theme page on WordPress.org | How widely the theme is used |
Read the reviews and the support tab. A pattern of the same complaint, such as broken layouts after updates or no reply from the author, tells you more than the star rating alone. Also check the changelog, which shows whether security fixes arrive promptly.
Look at the active install count as a weak signal, not proof. A theme with many installs gets more eyes on its code, but a popular theme can still ship a flaw. Use the install count with the other checks, never alone.
How do you run Theme Check on a theme?
Install the Theme Check plugin, open Appearance > Theme Check, pick your theme, and run the tests.
- Go to “Plugins > Add New”, search for “Theme Check”, then install and activate it.
- Go to “Appearance > Theme Check”.
- Select the theme you want to check and click “Check it!”.
- Read the results, which are grouped as Required, Warning, Recommended, and Info.
Theme Check runs all the same automated testing tools on your theme that WordPress.org uses for theme submissions (Theme Check). It holds a 4.8 out of 5 rating from 195 reviews, and its page was updated on 1 September 2026 (Theme Check).
Fix Required items first, since those block a theme from the directory. Warnings and Recommended items are worth fixing too, but they do not always mean the theme is unsafe. Theme Check is a helper tool, not an absolute measure, so use it with the other checks here.
Note the version number. The version number is the date of the revision of the guidelines used to create it, so a newer Theme Check version tests against newer rules (Theme Check).
What warning signs should you look for in theme code?
Look for obfuscated code, remote file loads from unknown servers, and functions that run code from theme options.
WordPress.org requires themes to be GPL-compatible, secure, and free of PHP or JavaScript notices, with all input sanitized and all output escaped (Theme Review).
A safe theme keeps design in the theme and features in plugins. WordPress.org forbids themes from bundling plugins or adding shortcodes, and themes must include at least index.php and style.css (Theme Review Requirements).
Block themes have a simpler structure. The only files a block theme needs are style.css, templates/index.html, and theme.json, which sets style properties in a structured way (Theme Structure). If a block theme ships dozens of PHP files with encoded strings, that is a warning sign.
Turn on WP_DEBUG on a staging copy to catch errors. The Theme Handbook says you should always enable debugging in a development environment so the theme shows no notices or errors (Debugging).
How do you check a theme for known vulnerabilities?
Search the theme name in a vulnerability database such as Patchstack or WPScan before you install it.
Only six vulnerabilities were reported in WordPress core in 2025, and Patchstack classed them as low priority, so the risk sits in themes and plugins (Patchstack).
Check whether the flaw has a fix. If the database shows an unpatched flaw in the theme version you plan to use, do not install it. If the flaw is fixed, check that the fixed version is the one you install.
Use the same method for plugins. Our guide to check a plugin for vulnerabilities walks through the same databases step by step.
How do you check a premium theme before you buy it?
Read the vendor's changelog, check how fast it answers support questions, and confirm it offers updates for at least a year.
A trustworthy vendor publishes a public changelog with dated releases. Look for regular updates, not a burst of releases followed by silence. If the changelog never mentions security fixes, ask the vendor how it handles them.
Check the refund and update terms before you pay. Most premium themes sell one year of updates and support, after which you must renew to keep getting fixes. A theme with no renewal path will stop getting security fixes after a year.
Search for the theme name plus words such as “vulnerability” or “hacked” to find public reports. A single old report with a fixed version is normal, but a pattern of unpatched flaws is a reason to pick another theme.
Theme.json version 3 arrived in WordPress 6.6, so a premium theme that still ships an old theme.json version may not be keeping up with current standards (Global Settings and Styles).
How do you test a theme safely before going live?
Test a new theme on a staging copy of your site, never on the live site, so a bad theme cannot break what visitors see.
Activate the theme on staging, then click through your key pages, forms, and checkout flow. Turn on WP_DEBUG while you test, since the Theme Handbook recommends debugging in a development environment to catch notices and errors (Debugging).
Run Theme Check on staging too, and check the browser console for failed requests. If the theme loads scripts from unknown domains, find out why before you go live.
If you do not have a staging site yet, set one up first. See how to set up a staging site for WordPress.
What mistakes should you avoid?
Do not install a theme from a random download site, and do not skip the update check because a theme looks good.
- Using a nulled theme, which can hide backdoors that no scanner will warn you about.
- Keeping a theme with no updates for over a year on a live site.
- Judging a theme only by its demo, which shows design, not code quality.
- Installing a theme that bundles plugins, since bundled copies do not update on their own.
- Activating a new theme on a live site without a backup or a staging test.
Check your themes on a schedule. Once a quarter, open Appearance > Themes, look for update notices, and replace any theme that has been abandoned by its author.
Frequently asked questions
Is it safe to use a free theme from WordPress.org?
Yes, if you check it first. Every theme on WordPress.org is hand-reviewed before listing, and you can see its last update, tested-up-to version, and reviews on its page. Run Theme Check after installing it, and keep it updated. Free themes from random download sites do not get the same review, so avoid them.
How do I know if my current theme has a vulnerability?
Search the theme name and version in a vulnerability database such as Patchstack, then check the theme changelog for a fix. If the flaw is unpatched, switch to another theme or contact the vendor. Also run Theme Check and turn on WP_DEBUG on a staging copy to catch code errors.
Should I use a child theme to customize my theme?
Yes. A child theme lets you change templates and styles without editing the parent theme, so updates do not wipe out your changes. If you edit the parent theme directly, the next update will overwrite your edits, and you may be tempted to skip updates that include security fixes.
What does GPL mean for a WordPress theme?
GPL is the GNU General Public License, the open-source license WordPress uses. WordPress.org requires themes in its directory to be 100% GPL or GPL-compatible, which means you can use, study, and change the code. A theme with an unclear license can hide restrictions or stolen code.
Can a theme slow down my site?
Yes. A theme that loads many scripts, fonts, or images can slow every page, and a poorly coded theme can add slow database queries. Check the theme on a staging site with your caching and speed tools, and compare load times before and after you switch themes.
Sources
- Theme Check WordPress.org
- How to do a review Make WordPress Themes
- Theme Review Requirements and Documentation Make WordPress Themes
- Theme Structure WordPress Developer Resources
- Debugging – Theme Handbook WordPress Developer Resources
- Global Settings and Styles (theme.json) WordPress Developer Resources
- State of WordPress Security in 2026 Patchstack
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
