WordPress security becomes real the morning your web developer forwards a government advisory and asks which version your site is running. You open the login page, try a password you have not typed in months, and realize you do not know the answer.
Most owners meet WordPress security the same way. The site was built once, it brings in leads or bookings, and nobody was ever told to look after it.
Here is the part people get wrong. A small site is not passed over because the business is small. The flaw in this story needs no account and no password, so an attacker does not need to know who you are, only which software you run.
What Happened in WordPress Core
On October 28, 2026, the WordPress project released version 7.1.4. Its release announcement calls it a security release and says “it is recommended that you update your sites immediately.” The first fix on the list is “a weakness in the WordPress upgrade process which can lead to remote code execution during the upgrade window.”
The flaw is tracked as CVE-2026-119977. Its record in the National Vulnerability Database was published on October 31, 2026 and lists WordPress Core versions 4.7 through 7.1.3 as affected.
On November 3, 2026, the U.S. Cybersecurity and Infrastructure Security Agency, known as CISA, added the flaw to its Known Exploited Vulnerabilities Catalog. The entry says WordPress Core “contains a time-of-check time-of-use (TOCTOU) race condition vulnerability that could allow unauthenticated attackers to execute code on the server during the upgrade window.” It adds: “This is due to predictable, web-accessible staging paths used during full-package core upgrades.”
In plain words, WordPress places its new files in a temporary folder while it installs a full update of itself. According to the CISA entry, that folder could be guessed and reached from the internet. Unauthenticated means the attacker does not have to sign in first.
The same day, the Canadian Centre for Cyber Security published its WordPress security advisory AV26-1117. It names WordPress Core prior to 7.1.4 as affected. It encourages users and administrators to review the linked pages and apply the necessary updates.
What is known, and what is not
A place in the CISA catalogue means the agency has recorded the flaw as exploited. Neither CISA nor the WordPress project has said who was attacked or how many sites were involved. The catalogue entry marks ransomware use as “Unknown”.
The dates tell you how seriously it was taken. The CISA entry was added on November 3, 2026 with a due date of November 6, 2026.
CISA’s directive BOD 26-04 describes that timeline as three days and applies it to federal agencies in the United States. That directive does not bind a Canadian business. It is still a fair measure of how fast the people who watch this every day decided to move.
Why a Small Business Website Is a Real Target
The Canadian Centre for Cyber Security explains the logic in its guidance on security considerations for your website. It says threat actors target web facing components, such as your web server, “because they are entry points to your network and data.” The same guidance warns that a compromised website may let a threat actor target other organizations and individuals you are affiliated with.
Think about what your site holds:
- Contact and quote forms: names, emails, phone numbers and whatever people type into the message box.
- Bookings and accounts: appointment details, customer logins and order history.
- Your reputation: the pages your customers trust, which an intruder who runs code on the server could change.
The guidance also makes a point about responsibility. It says your organization is legally responsible for protecting all customer data that is processed on your website, even if your organization does not host the website. Paying a host or a freelancer does not move that duty, so WordPress security stays on your own list.
How to Check Your WordPress Security Today
You can check the state of your WordPress security in about ten minutes, without touching any code. Do it yourself once, even if someone else maintains the site.
- Open the Updates screen. Sign in and go to Dashboard, then Updates. The WordPress documentation for the Dashboard Updates screen says a current site shows a message that you have the latest version and that “future security updates will be applied automatically.”
- Read the version number. The fixed release is 7.1.4. For older branches, the WordPress version 7.1.4 documentation lists the patched releases, from 7.0.8 and 6.9.11 down to 4.7.39.
- Confirm automatic updates are really on. The WordPress upgrade documentation says automatic updates are enabled by default “on most sites”. Most is not all, and a host or a developer may have switched them off.
- Check that the last update finished. The WordPress documentation on common errors explains that WordPress installs a .maintenance file while it updates. If visitors still see “Briefly unavailable for scheduled maintenance”, that file was not removed properly and the update needs attention.
- Find the update emails. The upgrade documentation describes update emails of three types: success, fail and critical. Find out which inbox receives them, and make sure a person reads it.
One caution on step 2. The version 7.1.4 documentation says the fixes were offered to older branches as a courtesy, and that only the most recent version of WordPress is actively supported. An old branch with a patch is a stopgap, not a plan.
The Real Gap Is Proof
Applying the patch is one click on most sites. The harder question comes later, from a customer, an insurer or a privacy regulator. They ask which version you were running on a given date, and when the update went in.
Most small businesses cannot answer that. The fix may have happened, but nobody can show it.
So write it down. Keep a short log with the date, the version number, who checked and what they saw. A dated screenshot of the Updates screen each month is enough to start, and it turns WordPress security from an assumption into something you can show.
WordPress Security Habits That Prevent the Next One
This will not be the last flaw in software your site depends on. Good WordPress security is a small set of habits, and each one below comes from official guidance.
- Leave automatic core updates on. The WordPress upgrade documentation says automatic background updates were introduced “in an effort to promote better security.”
- Remove plugins you do not use. The Canadian Centre for Cyber Security’s website guidance says to remove unnecessary plug-ins, because “the more plug-ins you have, the greater your attack surface is.”
- Protect the admin sign in. The same guidance says “we highly recommend enabling MFA for all types of accounts.” Multifactor authentication means a stolen password alone no longer opens the dashboard.
- Test your backups. The Canadian Centre for Cyber Security’s backup guidance says “test your backups to make sure they work” and recommends keeping a backup stored offline. The WordPress backup documentation adds: “Back up your database regularly, and always before an upgrade.”
- Put a web application firewall in front of the site. The website guidance describes it as a firewall that filters, monitors and blocks HTTP traffic, and says it can act as a short-term stopgap until a fix is applied. Our guide to web application firewall essentials explains how one works.
- Watch the site. The website guidance says to analyze logs and notify the appropriate parties of any unusual activities in a timely manner. Somebody has to be that appropriate party.
A firewall does not replace the update. It buys time, and the update closes the hole.
What PIPEDA Expects From a Business Website
If your site collects personal information, WordPress security is also a privacy matter. The Office of the Privacy Commissioner of Canada’s page on the PIPEDA safeguards principle says to protect personal information against loss, theft, or any unauthorized access. It lists security patches among the up-to-date technological tools a business can use.
That page also asks you to review safeguards regularly and to confirm you have addressed any known vulnerabilities. A core flaw named in a government advisory is a known vulnerability by any reading.
If an intruder does reach personal information, the Office of the Privacy Commissioner of Canada’s breach reporting guidance sets out three duties. You must report breaches that pose a real risk of significant harm to the commissioner, notify affected individuals, and keep records of all breaches. Your update log is part of how you show what happened and when.
Where Secur-IT Data Fits
Our cyber protection program for small and mid-sized businesses starts with an SMB Cyber Health Check. It reviews your external attack surface and internet-facing systems, along with patching and backup status. You receive a one-page risk snapshot and a prioritized remediation roadmap you can carry out with your IT provider or with our team.
For businesses that want ongoing cover, the managed tier adds 24/7 monitoring and alerting for users, endpoints and cloud platforms.
For small offices, the questionnaire-based assessment is free. Anything beyond that is quoted after a short scoping call, because a five page brochure site and an online store are not the same job.
Frequently Asked Questions
Q: What is the WordPress security flaw CISA listed in November 2026?
It is CVE-2026-119977, a race condition in the WordPress Core upgrade process. CISA’s Known Exploited Vulnerabilities Catalog says it could allow unauthenticated attackers to execute code on the server during the upgrade window. CISA added it on November 3, 2026.
Q: Which WordPress versions are affected, and which version fixes it?
The National Vulnerability Database record lists WordPress Core versions 4.7 through 7.1.3 as affected. WordPress 7.1.4, released on October 28, 2026, contains the fix, and the WordPress project also released patched versions for older branches.
Q: How do I check which WordPress version my site is running?
Sign in to the dashboard and open Updates. The WordPress documentation says a current site shows a message that you have the latest version. If you cannot sign in, ask whoever maintains the site to send you a dated screenshot of that screen.
Q: Are automatic updates enough to protect a small business website?
They are the most important single step in WordPress security, but not the whole job. WordPress says automatic updates are enabled by default on most sites, so confirm yours are on, confirm the last one finished, and keep a record of both.
Q: Does PIPEDA apply if my website is compromised?
If personal information was involved, yes, it can. The Office of the Privacy Commissioner of Canada says organizations must report breaches that pose a real risk of significant harm, notify affected individuals, and keep records of all breaches.
If you are not sure which version your site is running or who is watching it, our team at Secur-IT Data can help you find out and decide what to fix first.
References
- CISA: Known Exploited Vulnerabilities Catalog, CVE-2026-119977
- WordPress.org: WordPress 7.1.4 release announcement
- Canadian Centre for Cyber Security: WordPress security advisory (AV26-1117)
- Canadian Centre for Cyber Security: Security considerations for your website (ITSM.60.005)
- Office of the Privacy Commissioner of Canada: What you need to know about mandatory reporting of breaches of security safeguards
Ready to Strengthen Your Cybersecurity?
Secur-IT Data Solutions is a Toronto-based MSSP providing enterprise-grade cybersecurity for Canadian businesses. Whether you need OT security, AI threat protection, penetration testing, or full managed security services, our team is ready to help.
Talk to our team:
- 📞 Call us: +1 (647) 948-6768
- 📧 Email: info@securitdata.ca
- 🌐 Book a scoping call →

Krikor Tengerian is the CEO and founder of Secur-IT Data Solutions, a Toronto-based cybersecurity firm focused on helping Canadian organizations secure their infrastructure and critical systems. With over 25 years of experience across cybersecurity and IT infrastructure, he has supported organizations in hardening networks, protecting critical workloads, and aligning security controls with business and regulatory requirements.
Krikor actively shapes the direction and themes of Secur-IT’s educational content, collaborating with AI tools to structure, refine, and expand articles while providing the real-world context, use cases, and review to keep them accurate and practical for readers. He regularly shares insights on OT security, threat detection, incident response, and Canadian cybersecurity compliance to help industrial and commercial organizations better understand and reduce their cyber risk.




