A newly announced set of critical PHP flaws is a reminder of an uncomfortable truth: many of the cybersecurity threats facing your practice are beyond your direct control, but the HIPAA responsibility is not.
Your practice runs on software you did not write, hosted in data centers whose firewalls and security systems you do not manage. You depend on software vendors and cloud providers to find vulnerabilities, apply patches and maintain safeguards. But when a breach happens, it is your office's responsibility. Patients will not call your software vendor. They will call you, and the distrust, reputational damage and lost income land on your practice.
Here is what was announced, why it matters even if your technology is fully outsourced, and how to protect your practice.
The latest example: critical PHP flaws could let attackers take over web servers
CISA and the Multi-State Information Sharing and Analysis Center (MS-ISAC) have warned of two critical vulnerabilities in PHP, CVE-2026-109618 and CVE-2026-109619. An attacker could exploit them remotely, without logging in, to run their own code on an affected server.
PHP is the programming language behind a huge share of the web, including many practice websites, patient portals, online intake and appointment forms, and WordPress sites. If your site collects any patient information, it may be running PHP.
- Who is at risk: every PHP installation that serves web requests.
- Affected versions: PHP releases before 8.2.35, 8.3.36, 8.4.27 and 8.5.12, plus PHP 8.1 and earlier.
- Exploitation so far: none reported in the wild when the advisory was issued, which means now is the window to patch before attackers catch up.
- The fix: update PHP after testing. Temporary mitigations reduce some attack paths but are not a complete fix.
Most practices never touch PHP directly. It runs inside websites, portals and applications managed by your vendors, which means the patch is in their hands. That is exactly the point.
Ask your website host, patient portal vendor and software providers: Do our systems run PHP, and have these updates been applied?
Beyond your control, but not beyond your responsibility
If a vulnerability at one of your vendors leads to unauthorized access to your patients' protected health information (PHI), your practice may still carry significant legal, regulatory, financial and operational responsibilities. That holds even when the breach starts with a software company or cloud hosting provider.
Your practice may be responsible for:
- Evaluating the incident and what patient information was involved.
- Determining whether HIPAA breach notification requirements apply.
- Notifying affected patients and government authorities when required.
- Documenting your response from start to finish.
Your vendor may have its own HIPAA obligations, but that does not relieve your practice of yours. In the eyes of regulators and patients alike, the breach is your office's problem to answer for.
A breach is a business problem, not just an IT problem
Patients trust your practice with their most personal information. They do not know or care which vendor hosted their records. When a breach letter arrives with your name on it, your practice is the one they hold accountable.
The fallout reaches far beyond compliance:
- Lost trust. Patients who feel their information was mishandled may question whether to stay with your practice.
- Damaged reputation. Breach notices, online reviews and word of mouth can undo years of marketing and goodwill in a few weeks.
- Fewer new patients and referrals. Prospective patients and referring doctors notice a practice in the news for the wrong reasons.
- Disrupted income. Systems taken offline, staff pulled into incident response, notification costs and delayed billing all hit revenue directly.
The best protection is preparation, so a vendor's problem does not become a crisis for your practice.
What protects your practice
You cannot patch your vendors' systems, but HIPAA expects you to manage the risk they pose. Three safeguards do most of the work:
- Business Associate Agreements. Every vendor that creates, stores or transmits PHI for your practice needs a signed BAA spelling out how it will protect that data and when it must tell you about a breach.
- Vendor security evaluation. Know which vendors hold your patient data, ask how they secure that information, and include them in your annual risk analysis.
- A documented incident response plan. When a vendor reports a breach, your staff should know who evaluates it, how the notification decision is made, and where the response is recorded.
Documentation matters too. If a breach happens, regulators will ask what you knew, when, and what you did about it. An up-to-date risk analysis, mitigation plan and HIPAA manual show a good-faith compliance program, and correcting a problem promptly can make a real difference in how penalties are handled.
A vendor security checklist for your practice
Use this list at your next staff or IT meeting:
- List every vendor and cloud service that stores or transmits patient data.
- Confirm each one has a signed, current Business Associate Agreement.
- Ask your website, portal and software vendors to confirm they have applied the PHP updates.
- Find out how each key vendor will notify you of a security incident, and how fast.
- Include vendor risks in your annual HIPAA risk analysis.
- Keep a written incident response plan that covers breaches that start at a vendor.
- Require multi-factor authentication on vendor portals, email and the EHR.
- Train staff to recognize phishing emails, a leading cause of healthcare breaches.
You don't have to manage HIPAA compliance alone
TLD Systems helps medical practices turn security alerts like these into a clear, documented compliance plan. The program was built by Dr. Brody, a practicing podiatrist and the company's CEO, who knows firsthand how hard it is to keep up with regulations while caring for patients.
The Comprehensive HIPAA Compliance Program follows a three-step roadmap:
1. Risk Analysis: identify the physical, technical and administrative safeguards already in place.
2. Risk Mitigation Plan: use TLD Systems' customized risk rankings to pinpoint your office's biggest risks and reduce the chance of a patient data breach.
3. Maintain a Culture of Compliance: keep an up-to-date HIPAA manual and trained staff, so you are prepared if a breach ever occurs.
The program includes:
- HIPAA training for doctors and staff
- A customized HIPAA manual
- A practice-specific Notice of Privacy Practices
- Business Associate Agreement forms and tracking
- Annual risk analysis completion
- OSHA bloodborne pathogen training
Our hands-on customer service keeps you on track, so you can remove the regulatory speed bumps and focus on what matters most: patient care.
Contact TLD Systems today to learn more or sign up for the HIPAA Compliance Program.
- Call: 631-403-6687
- Email: info@TLDSystems.com
- Visit: www.TLDSystems.com
Vulnerability details are based on advisories from CISA and MS-ISAC. This article is for general information and is not legal advice.

Read Comments