Skip to main content

A note to our neighbours · Southern Tasmania

THE INTERNET
IS ON FIRE.

Your business doesn't have to be.

10 local businesses. Free, personally reviewed website exposure checks.

No bullshit. No obligation. An enquiry doesn't reserve a place.

The internet has had an absolute shocker. Running a café, orchard or workshop doesn't leave much time to follow security alerts. Start with three things your website provider should be able to demonstrate: what's running, whether it was exposed, and whether you can recover. Your website might be fine. Let's establish what we can actually verify.

November: what needs checking now?

Reviewed 13 November 2026. Hosting, trusted applications and backups: check what applies to your business. Incident and disclosure dates are shown separately from this review.

MICROSOFT DISCLOSURE AND CISA LISTING · 10 NOVEMBER UTC

Outlook on Windows: confirm the security update landed.

Microsoft published fixes for Outlook spoofing flaw CVE-2026-124194, and CISA added it to its known-exploited catalogue. Microsoft's affected-product list includes Microsoft 365 Apps for Enterprise and Office LTSC 2021/2024 on Windows. This is a targeted update check, not evidence your mailbox or business has been compromised.

Useful action: ask whoever manages your computers to apply the relevant November Office security update and verify the installed build for your servicing channel. If updates are centrally managed, ask for confirmation across staff computers, not just one machine. Treat unexpected files cautiously while the update is being arranged.

Microsoft's CVE record and affected products · CISA's official catalogue

NEW SECURITY DISCLOSURE · 5 NOVEMBER

Alpine servers: check the remote login service.

OpenSSH released a critical fix for a password-login bypass affecting particular Linux configurations. Alpine says affected servers can admit an attacker without the account's password. This requires a running SSH service and specific authentication/account settings; it does not affect every Linux server or ordinary container.

Useful action: ask your host whether it runs Alpine with SSH and whether the advisory applies. If it does, ask them to install the vendor's fixed package and restart the SSH service, then verify it. Installing the package alone leaves the old service running. Have the provider preserve working administrative access while making changes.

Exploitation update, 9 November: CISA added this flaw, now identified as CVE-2026-123158, to its known-exploited catalogue. That strengthens the reason to check affected servers promptly; it is new exploitation evidence about the 5 November disclosure, not a new flaw or proof your server was attacked. CISA's official catalogue.

Alpine's 5 November advisory →

OBSERVED FROM 1 NOVEMBER · REPORTED 3 NOVEMBER, UPDATED 4 NOVEMBER

Microsoft 365: who else has the keys?

Todyl reports stolen application credentials being used to access Microsoft 365 and Azure, including IT providers' customer environments. This is credential abuse, not a newly discovered Microsoft software flaw.

Useful action: if an IT provider manages your email or cloud files, ask them to review trusted applications, delegated access and application sign-in logs, and investigate unexpected access. Keep MFA enabled for people; it doesn't cover every application identity. Ask who will contain affected access and replace exposed credentials if evidence is found.

Todyl's investigation · Microsoft's application-identity guidance

NEW INCIDENT · 1–2 NOVEMBER

Ask your host whether it uses cPGuard.

OPSSHIELD says attackers compromised its infrastructure and distributed a malicious cPGuard update on 2 November. This is hosting security software: your provider may run it even if you've never heard of it.

Useful action: ask whether your server received the affected update. The vendor calls for cPGuard 5.88.25 or later and, where the malicious script ran or may have run, treatment as a compromise and replacement of affected passwords and keys. Cleanup does not undo stolen credentials. Ask for the host's evidence and recovery plan; don't try server-repair commands yourself.

OPSSHIELD's response guidance →

NEW EXPLOITATION LISTING · 3 NOVEMBER

WordPress: check core updates, too.

CISA added WordPress Core CVE-2026-119977 to its known-exploited catalogue on 3 November. The flaw can allow code execution during a core upgrade. WordPress released the security fix in 7.1.4 on 28 October; the November listing isn't a new disclosure or proof that your site was attacked.

Useful action: ask your provider to confirm that the relevant core security update actually completed, alongside plugin, theme and PHP updates. Check any earlier exposure and relevant logs. “Automatic updates are switched on” is not confirmation that an update succeeded.

If you still need the fix: Xint's 3 November research shows that the old updater can remain vulnerable during the first full-package upgrade. Ask your host to protect the temporary upgrade directory from public web access before that update, using a supported process. Don't indefinitely postpone patching. This is added update guidance, not a new November vulnerability. Xint's research and update guidance.

Taking bookings with LatePoint? A separate flaw, CVE-2026-118066, was disclosed on 6 November UTC. Versions through 5.7.6 can allow customer-account takeover, exposing bookings and personal information. Ask your provider to update the plugin to the current supported release (5.7.8 at this review) and check unexplained customer-password resets or account changes. The fix shipped in 5.7.7 on 2 November. This is customer-account risk, not a claim that every WordPress administrator account is vulnerable or that your site was attacked. Wordfence's CVE record · LatePoint release history.

Accepting files through Ninja Forms? The premium File Uploads add-on, not Ninja Forms core generally, has a file-deletion flaw disclosed on 11 November (CVE-2026-126537). If you use this add-on, ask your provider to check its version and update 3.3.36 or earlier to 3.3.37 or later. If patching is delayed, agree how to disable the affected upload function without losing essential enquiries. Investigate unexplained missing files; an update won't restore deleted data. Wordfence's CVE record · Affected and fixed versions.

WordPress security release · CISA catalogue (official mirror)

Hosting updates and catch-ups

October catch-ups: still worth resolving

Being patched today doesn't prove you weren't exposed yesterday. It also doesn't prove there was a compromise. Those questions need different evidence.

Three questions for your website provider

  1. 1. Are we running affected software?

    Ask for WordPress core (if used), plugins, themes, PHP, hosting security and remote-management tools to be checked. Are they supported and patched? Which administration services are publicly reachable, and do they need to be? Somebody should know what's running underneath your website.

  2. 2. Were we exposed before it was patched?

    What evidence exists of exploitation or compromise? Have relevant logs and alerts been reviewed? What can't be established from the records available? If credentials were exposed, which passwords, keys and sessions need replacing or revoking? A clean update alone may not remove an attacker's access.

  3. 3. Who is responsible if something goes wrong?

    Who manages hosting, backups, security updates and incident response? When was a backup last successfully restored, and is a recoverable copy kept separately from the live site? Use multi-factor authentication for email, hosting and administrator accounts. Can you reach the responsible person when it matters?

Send this to your provider

Hi, could you help me check our website security? Could you confirm our WordPress core (if used), plugins, themes and PHP runtime are on supported, patched releases, including PHP2Shell (CVE-2026-109618 and CVE-2026-109619)? Does our hosting use cPGuard or remote-management software affected by a recent incident? Please confirm whether we were exposed before patching, what logs were checked, whether affected passwords, keys or sessions need replacing, and when a backup was last successfully restored. Who owns each action? A short written update, including anything you cannot establish, would be appreciated. Thanks.

You can also select the message above and copy it into an email. No registration needed.

10 local businesses. Free exposure checks.

The first ten eligible businesses receive a personally reviewed initial website exposure assessment, with a short written report in plain English.

Genuinely free. No obligation. No purchase required.

This is an initial external review, not a full penetration test, forensic investigation, compliance certification or guarantee of security. No exploit attempts or intrusive testing are included.

Who it's for

Businesses in the Huon Valley and southern Tasmania with a public website. Sole traders, family businesses and small not-for-profits are welcome. I'll confirm local eligibility and your authority to represent the website by email. No website yet? The local services page is a better starting point.

Eligible places are allocated in the order enquiries arrive, after review. Duplicate enquiries don't get extra places. I'll confirm an award in writing; submitting an enquiry doesn't secure one. The ten-place limit includes completed assessments.

This free review is separate from my paid business diagnostic and implementation work. It isn't a first step you must take towards buying anything.

What you'll receive

Illustrative example · fictional business

Initial website exposure review

Example Orchard · example.invalid
Example assessment date: 25 October 2026

Observed
Public site served over HTTPS. Underlying PHP runtime version not externally verifiable. Hosting ownership not yet confirmed.
Potential concern
PHP2Shell exposure cannot be ruled in or out from public observations.
Next action
Ask the hosting provider to confirm the PHP runtime, patch status and relevant log review.
Confidence and outcome
Limited by external-only access. Provider verification required; no conclusion of compromise.

An unanswered question is not a confirmed vulnerability. A lack of visible problems is not a security certificate.

Request a free check

Email me using the draft below. Include your business name, public website URL, town or suburb, contact name and email, and confirmation that you own or are authorised to represent the website. A short concern is optional.

Please don't send passwords, API keys, hosting credentials, customer records, payment details or sensitive files.

Open an email draft

This opens your email app. You still need to complete and send the email. Nothing has been submitted by clicking. If it doesn't open, email adrian@adrianwedd.com with the subject “ON FIRE — free website exposure review”.

Show the application text to copy
Hi Adrian,

I'd like to request the free initial website exposure review.

Business name:
Public website URL:
Business location (town/suburb):
Contact name:
Contact email:
Optional concern (no sensitive details):

Authority: [Please confirm: I own or am authorised to represent this website.]

I understand this is an enquiry, not an awarded place, and that the review is external and non-invasive.

I'll reply to confirm receipt and check eligibility. A place is awarded only when I confirm that separately in writing. If you haven't heard back within three business days, follow up by email. Please keep any follow-up in the same thread.

Enquiry information is used to check eligibility, allocate places and deliver the review. It is held in my Google-hosted email account and a private local campaign record, accessible to me and the providers operating that infrastructure. Participant identities and findings aren't published or added to marketing lists. Campaign records and assessment correspondence are scheduled for deletion 90 days after the offer closes, unless you ask me to retain them or a legal requirement applies; provider backups may take longer to expire. Privacy details and deletion requests.

I'm Adrian. I'm in Cygnet.

I build and investigate software systems, from local business tools to adversarial testing of AI. My work spans cybersecurity, reliability and finding out what systems actually do when things go wrong. This is me offering a bounded piece of useful work to my neighbours.

More about my background · Adversarial evaluation work · Local services

Sources and updates

Prepared: . Last reviewed: . Published: .

Change history

Advisories can change. Internet Fire Watch informs the daily editorial review; we publish when evidence or useful advice changes. A quiet day does not trigger a new timestamp. Incident dates above are separate from this page's review date. The later LiteLLM investigation corrects parts of its initial explanation. Spotted something outdated? Email a correction.