<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Vijay Mishra on Medium]]></title>
        <description><![CDATA[Stories by Vijay Mishra on Medium]]></description>
        <link>https://medium.com/@vijaysuper11?source=rss-4dea5301688c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*tX43TGJBegwtAHFycTtmHw.png</url>
            <title>Stories by Vijay Mishra on Medium</title>
            <link>https://medium.com/@vijaysuper11?source=rss-4dea5301688c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 01:38:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vijaysuper11/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Apache HTTP Server 2.4.71: Update Now to Fix the mod_http2 Flaw (CVE-2026–119618)]]></title>
            <link>https://medium.com/@vijaysuper11/apache-http-server-2-4-71-update-now-to-fix-the-mod-http2-flaw-cve-2026-119618-3385f39644eb?source=rss-4dea5301688c------2</link>
            <guid isPermaLink="false">https://medium.com/p/3385f39644eb</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Vijay Mishra]]></dc:creator>
            <pubDate>Fri, 13 Nov 2026 16:41:58 GMT</pubDate>
            <atom:updated>2026-11-13T16:41:58.826Z</atom:updated>
            <content:encoded><![CDATA[<p>If your website runs on Apache, this week brings one update worth doing soon. On November 11, 2026, the Apache Software Foundation released Apache HTTP Server 2.4.71, which fixes a critical flaw in the HTTP/2 module. The good news is that the fix is already out, and for most people the job is one update and a quick check.</p><h3>What was fixed</h3><p>The flaw is tracked as CVE-2026–119618. According to the official Apache security page, it is a race condition in mod_http2, in a function called assign_headers(). Two parts of the code can touch the same data at the same time without proper coordination, which can corrupt memory on the server. In the worst case, an unauthenticated attacker could run code with the web server&#39;s privileges.</p><p>Apache rates it Critical. Both Apache’s own page and BleepingComputer’s report list the same affected range: Apache HTTP Server 2.4.55 through 2.4.70, plus the standalone mod_h2 module from GitHub, versions 2.0.8 through 2.0.42.</p><p>The same release also fixes CVE-2026–106023, a crash bug in mod_md rated Important, and a low-severity issue in mod_vhost_alias.</p><h3>Who should pay attention</h3><p>Three groups of people are most likely to be affected:</p><ul><li>Anyone who manages their own VPS or dedicated server running Apache.</li><li>Agencies and developers who look after client servers.</li><li>Site owners on managed hosting, who should simply ask their host whether the server has been updated.</li></ul><p>BleepingComputer, citing Wiz telemetry, notes that HTTP/2 has to be enabled for the flaw to matter, and that it is not on by default. At the same time, Wiz found vulnerable resources in 64% of the cloud environments it looks at, and about half of those had publicly exposed instances. Those numbers do not account for configuration, so your own setup may be safer than the average. The only way to know is to check.</p><p>As of the reports published on November 12, Wiz said it was not aware of public exploits or attacks. That can change, which is a good reason to act early rather than wait.</p><h3>What to do</h3><ol><li><strong>Check your version.</strong> Run apachectl -v or httpd -v. If it shows something between 2.4.55 and 2.4.70, you need the update.</li><li><strong>Update to 2.4.71 or later.</strong> On most Linux systems this means your package manager. If your distribution has not published 2.4.71 yet, look for a backported security fix in its advisories.</li><li><strong>Restart Apache</strong> after updating, and confirm the new version is running.</li><li><strong>If you cannot update today,</strong> the security firm watchTowr suggests disabling HTTP/2 until you can. Remove or comment out the h2 entry in your Protocols line, then reload. Your site keeps working over HTTP/1.1, just without the HTTP/2 speed benefits.</li><li><strong>If you use standalone mod_h2,</strong> move to a fixed release, not only the main Apache package.</li></ol><h3>Why HTTP/2 keeps showing up in security news</h3><p>This is not the first HTTP/2 fix of the year. In May, Apache 2.4.67 closed CVE-2026–23918, a double-free bug in mod_http2 with a CVSS score of 8.8. In June, the Node.js project also shipped HTTP/2 fixes in its 2026 security releases.</p><p>The pattern makes sense. HTTP/2 is a busy protocol with many streams sharing one connection, so small timing mistakes can matter. As more of the web depends on it, more researchers look at it, and more of the issues they find get fixed. According to Apache’s page, this latest bug was found by Anthropic’s OSS Scanner and by Google Cloud Vulnerability Research, which shows automated tools and human researchers are both helping here.</p><p>For site owners, the lesson is calm and practical: keep the web server itself on a regular update schedule, not only WordPress and plugins.</p><h3>A short checklist</h3><ul><li>Know which web server and version each of your sites runs.</li><li>Update Apache to 2.4.71 or later.</li><li>Restart and verify the version afterwards.</li><li>Disable HTTP/2 temporarily if an update is not possible yet.</li><li>Keep a recent backup before any server change.</li><li>Ask your hosting provider about their patch timing if you are on managed hosting.</li><li>Re-check your site after the update: homepage, forms, checkout and login.</li></ul><p>Server updates are much less stressful when they are routine. If you would like a hand with updates, backups and monitoring, I share more website care tips at <a href="https://expertwebdeveloper.in/">expertwebdeveloper.in</a> and <a href="https://growsmartwithai.com/">growsmartwithai.com</a>.</p><h3>Sources</h3><ul><li><a href="https://httpd.apache.org/security/vulnerabilities_24.html">Apache HTTP Server 2.4 security vulnerabilities</a></li><li><a href="https://bleepingcomputer.com/news/security/apache-http-server-patches-critical-http-2-remote-code-execution-flaw">BleepingComputer: Apache HTTP Server patches critical HTTP/2 remote code execution flaw</a></li><li><a href="https://securityonline.info/apache-http-server-cve-2026-119618-rce-fixed/">Security Online: CVE-2026–119618, Apache HTTP Server remote code execution fixed in 2.4.71</a></li><li><a href="https://www.trackr.live/?p=618">Trackr: Apache HTTP/2 double-free in mod_http2 (CVE-2026–23918)</a></li><li><a href="https://nodejs.org/en/blog/vulnerability/june-2026-security-releases">Node.js June 2026 security releases</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3385f39644eb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chrome Zero-Day CVE-2026–125350: How to Update Chrome and Edge Today]]></title>
            <link>https://medium.com/@vijaysuper11/chrome-zero-day-cve-2026-125350-how-to-update-chrome-and-edge-today-e9427b7618ea?source=rss-4dea5301688c------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9427b7618ea</guid>
            <category><![CDATA[chrome]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Vijay Mishra]]></dc:creator>
            <pubDate>Thu, 12 Nov 2026 13:36:51 GMT</pubDate>
            <atom:updated>2026-11-12T13:51:21.954Z</atom:updated>
            <content:encoded><![CDATA[<p>If you opened Chrome this week, there is a good chance it is still running a build from before Monday. Google shipped a fix on November 9 for a bug that attackers were already using, and the update reaches people gradually, so it is worth checking by hand. The whole check takes about two minutes.</p><p>This guide explains what the Chrome zero-day CVE-2026–125350 is, which versions carry the fix, and what a small team can do about it today.</p><h3>What happened</h3><p>CVE-2026–125350 is a use-after-free bug in the XML component of Chrome. Google rates it High and says it is aware that an exploit exists in the wild. An anonymous researcher reported it on November 6, and the fix arrived in the Stable channel on November 9, three days later.</p><p>CISA added the flaw to its Known Exploited Vulnerabilities catalog on November 10. Its entry describes a specially crafted web page that could let an attacker run code inside the browser sandbox. Google has not shared who was targeted or how, which is normal while people are still updating.</p><p>The same release fixed nine security issues in total. One of them, CVE-2026–125346, is also an XML use-after-free, but Google has only said that CVE-2026–125350 is exploited. Industry commentators count it as Chrome’s eighth zero-day of 2026.</p><h3>Which versions have the fix</h3><p>Chrome 157 reached Stable on November 3. Builds from that first release do not include this fix. You want one of these or newer:</p><ul><li>Windows and macOS: 157.0.8103.50/.51</li><li>Linux: 157.0.8103.50</li><li>Android: 157.0.8103.50</li><li>Extended Stable (Windows and macOS): 156.0.8078.96</li></ul><p>At the time of writing, ChromeOS had no Stable update listing this fix, so Chromebook users should keep checking their update page.</p><h3>What to do: update Chrome in four steps</h3><ol><li>Open Chrome and go to the three-dot menu, then Help, then About Google Chrome.</li><li>Let it download the update. The page shows your version number.</li><li>Click Relaunch. The patch does not apply until the browser restarts.</li><li>Open About Google Chrome once more and confirm the number matches the list above or is higher.</li></ol><p>Keep your tabs in mind before relaunching. Chrome offers to restore them, so you will not lose your place.</p><h3>What to do: Edge, Opera, Brave and others</h3><p>Because the bug lives in Chromium, other browsers built on it can be affected too. Microsoft Edge receives the fix through its own update, so open edge://settings/help, let it check, and restart. I could not find a confirmed Edge version number in the sources, so rather than quote one, I suggest checking that Edge reports it is up to date.</p><p>Opera, Brave and Vivaldi publish their own builds. Check each vendor’s release notes, and update as soon as a build that lists the Chromium fix appears.</p><h3>What to do for a small business or website team</h3><p>Browsers are easy to forget because they update themselves. A few habits make this routine:</p><ul><li>Ask everyone on the team to open the About page and relaunch today.</li><li>If you manage company laptops, push the new version through your device management tool and set a short deadline for the restart.</li><li>Remind people who keep Chrome open for weeks that the restart is the step that counts.</li><li>Check any kiosk, reception or shared computers, which often miss updates.</li><li>If you run a website, nothing needs changing on your server for this one. It is a visitor-side issue, so the useful step is making sure your own team is covered.</li></ul><h3>A wider trend worth noting</h3><p>This was not the only exploited bug added to the CISA list on November 10. A Microsoft Outlook flaw, CVE-2026–124194, that can expose NTLM hashes was added the same day, and Microsoft fixed it in its November Patch Tuesday release. The pattern is the same each time: a fix exists, and the gap is the time between release and installation.</p><p>For a small team, the simplest defence is a short, regular routine. Pick one day a week to confirm browsers, operating systems and plugins are current, and treat any “exploited in the wild” headline as a reason to do it sooner.</p><h3>Quick checklist</h3><ul><li>Chrome shows 157.0.8103.50 or newer (Linux and Android), or 157.0.8103.50/.51 or newer (Windows and macOS)</li><li>Browser has been relaunched after the update</li><li>Edge reports it is up to date</li><li>Other Chromium browsers checked against their vendor notes</li><li>Team members and shared computers covered</li><li>A weekly update check is on the calendar</li></ul><h3>Closing</h3><p>Updates like this one are a reminder that the quickest security win is often the plainest one. If you would like a second pair of eyes on your website or your team’s setup, the free health check and care plans at <a href="https://expertwebdeveloper.in/">expertwebdeveloper.in</a> are a friendly place to start, and more practical guides live at <a href="https://growsmartwithai.com/">growsmartwithai.com</a>.</p><p>This guide is also available on <a href="https://growsmartwithai.com/blog/chrome-zero-day-cve-2026-125350-update/">growsmartwithai.com</a>, <a href="https://expertwebdeveloper.in/blog/chrome-zero-day-cve-2026-125350-update/">expertwebdeveloper.in</a>, <a href="https://dev.to/vijay_mishra_14dd027a16ee/chrome-zero-day-cve-2026-125350-how-to-update-chrome-and-edge-today-np4">dev.to</a>, <a href="https://iamvijaymishra.substack.com/p/chrome-zero-day-cve-2026-125350-how">Substack</a> and <a href="https://www.linkedin.com/pulse/chrome-zero-day-cve-2026-125350-how-update-edge-today-vijay-mishra-bdxtc/">LinkedIn</a>.</p><h3>Sources</h3><ul><li>Google Chrome Releases, Stable Channel Update for Desktop, November 9, 2026 (summarised by <a href="https://www.rescana.com/post/google-chrome-cve-2026-125350-xml-use-after-free-exploited-patch-now">Rescana</a> and <a href="https://smartscope.blog/en/blog/chrome-157-157-0-8103-50-9-security-2026/">SmartScope</a>)</li><li><a href="https://www.cisa.gov/news-events/alerts/2026/11/10/cisa-adds-six-known-exploited-vulnerabilities-catalog">CISA: Adds Six Known Exploited Vulnerabilities to Catalog, November 10, 2026</a></li><li><a href="https://socradar.io/blog/cve-2026-125350-google-chrome-xml-0day/">SOCRadar: CVE-2026–125350, Google Fixes Exploited Chrome XML Zero-Day</a></li><li><a href="https://www.csoonline.com/article/4247015/november-2026-patch-tuesday-63-critical-microsoft-fixes-plus-an-outlook-zero-day-that-allows-theft-of-hashed-credentials.html">CSO Online: November 2026 Patch Tuesday</a></li><li><a href="https://www.chromegeek.com/chrome-zero-day-cve-2026-125350/">Chrome Geek: Update Chrome Now</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9427b7618ea" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WordPress Security Update: How to Fix CVE-2026–119977 in 15 Minutes]]></title>
            <link>https://medium.com/@vijaysuper11/wordpress-security-update-how-to-fix-cve-2026-119977-in-15-minutes-a8bcd4227875?source=rss-4dea5301688c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8bcd4227875</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[wordpress]]></category>
            <dc:creator><![CDATA[Vijay Mishra]]></dc:creator>
            <pubDate>Mon, 09 Nov 2026 08:06:21 GMT</pubDate>
            <atom:updated>2026-11-09T08:06:21.941Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rx1bqBkbDKlEh9YM-fNQ2w.png" /></figure><p>If you run a WordPress site, this is a good week to check your version number. A flaw in the way WordPress updates itself, tracked as CVE-2026–119977, was added to the US CISA list of known exploited vulnerabilities on November 3, 2026. The fix is already available, and applying it takes a few minutes.</p><p>This guide explains what happened in plain language and gives you a short list of steps to follow.</p><h3>What happened</h3><p>WordPress released version 7.1.4 on October 28, 2026. It is a security release, and it includes a fix for a race condition in the core update process. The issue is rated 8.1 (high) and affects WordPress versions 4.7 through 7.1.3.</p><p>Here is the idea behind it. When WordPress runs a full core update, it unpacks the new files into a staging folder inside wp-content/upgrade/. In affected versions that folder name was predictable and could be reached from the web. During the short time the update was running, a visitor with no account could try to use those staged files and run code on the server.</p><p>Wordfence reported more than 18,500 requests aimed at these staged installer paths in the first 21 hours after the details became public. Those are attempts, and security teams have not described them as confirmed break-ins. Still, CISA listing it means real-world use has been seen, so it is worth treating as a priority.</p><h3>Which versions are fixed</h3><p>WordPress backported the fix to older branches. These are the patched versions Wordfence lists:</p><ul><li>7.1 branch: 7.1.4</li><li>7.0 branch: 7.0.8</li><li>6.9 branch: 6.9.11</li><li>Older branches down to 4.7 also received patches</li></ul><p>If you are on an old branch, the better long-term move is to upgrade to the current release, since only the latest version is actively supported.</p><h3>What to do: update WordPress core</h3><p><strong>What to do:</strong> Open Dashboard, then Updates, and install the offered version. Confirm the number shows 7.1.4 or the fixed release for your branch. If you use WP-CLI, run wp core version to check and wp core update to update.</p><p>Do not assume an automatic update finished. Look at the version number yourself.</p><h3>What to do: block the upgrade folder</h3><p><strong>What to do:</strong> Ask your host, or set a rule on your web server, to deny web access to PHP files inside wp-content/upgrade/. That folder is only meant for WordPress to use during updates, so visitors never need to reach it. If you use a firewall plugin such as Wordfence, check that its protection is switched on. Sites on the free Wordfence plan receive new rules later than paid plans, so the server rule is a useful extra layer there.</p><h3>What to do: look through your logs</h3><p><strong>What to do:</strong> Search your access logs for requests to setup-config.php under wp-content/upgrade/. If you find none, that is good news. If you find some, check that your wp-config.php file and your list of administrator users look the way you expect, and change your passwords as a precaution.</p><h3>What to do: update plugins at the same time</h3><p>Core was not the only thing in the news. Patchstack reported attacks on the Bricksforge plugin (CVE-2026–85097), which was fixed in version 3.1.8.10. Elementor Pro versions up to 4.2.1 had a file upload issue (CVE-2026–32475) that was fixed in 4.2.2. If you use either one, check that you are on the fixed version.</p><p>The wider habit is simple: update plugins and themes at least once a week, and remove any you no longer use.</p><h3>A pattern worth noticing</h3><p>Attackers now begin scanning within hours of a patch going public. WordPress 7.1.4 came out on October 28, and probing began the same week. That means a long gap between a release and your update is the riskiest period. Turning on automatic updates for core security releases, together with regular backups, shortens that gap a lot.</p><h3>Quick checklist</h3><ol><li>Check your version and update to 7.1.4 or the fixed release for your branch.</li><li>Block PHP access to wp-content/upgrade/.</li><li>Search logs for setup-config.php requests in that folder.</li><li>Update Bricksforge and Elementor Pro if you use them.</li><li>Make sure a recent backup exists.</li><li>Remove plugins you do not use.</li></ol><h3>Closing thought</h3><p>This one is easy to deal with: a single update closes the door. If you would like a hand checking several sites, setting up safe automatic updates or reviewing your logs, the team at <a href="https://expertwebdeveloper.in/">Expert Web Developer</a> is happy to help. More guides are on <a href="https://growsmartwithai.com/">Grow Smart with AI</a>.</p><h3>Sources</h3><ul><li><a href="https://thehackernews.com/2026/11/cisa-confirms-hackers-exploiting.html">The Hacker News, CISA Confirms Hackers Exploiting WordPress Core Flaw During Software Upgrades</a></li><li><a href="https://www.cisa.gov/news-events/alerts/2026/11/03/cisa-adds-one-known-exploited-vulnerability-catalog">CISA, CISA Adds One Known Exploited Vulnerability to Catalog (November 3, 2026)</a></li><li><a href="https://www.picussecurity.com/resource/blog/cve-2026-119977-when-updating-wordpress-becomes-the-vulnerability">Picus Security, CVE-2026–119977: When Updating WordPress Becomes the Vulnerability</a></li><li><a href="https://patchstack.com/articles/wordpress-7-1-4-security-release/">Patchstack, WordPress 7.1.4 Security Release</a></li><li><a href="https://digital.nhs.uk/cyber-alerts/2026/cc-4884">NHS England Digital, WordPress Releases Security Update Addressing Multiple Vulnerabilities</a></li><li><a href="https://www.securityweek.com/bricksforge-wordpress-plugin-vulnerability-exploited-in-the-wild/amp/">SecurityWeek, Bricksforge WordPress Plugin Vulnerability Exploited in the Wild</a></li><li><a href="https://www.securityweek.com/elementor-pro-wordpress-plugin-vulnerability-exploited-to-hack-sites/">SecurityWeek, Elementor Pro WordPress Plugin Vulnerability Exploited to Hack Sites</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8bcd4227875" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Shopify Checkout Redirect: How to Check Your Store and Your Apps]]></title>
            <link>https://medium.com/@vijaysuper11/shopify-checkout-redirect-how-to-check-your-store-and-your-apps-e9692a7e8d7d?source=rss-4dea5301688c------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9692a7e8d7d</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[shopify]]></category>
            <category><![CDATA[ecommerce]]></category>
            <dc:creator><![CDATA[Vijay Mishra]]></dc:creator>
            <pubDate>Wed, 04 Nov 2026 14:00:48 GMT</pubDate>
            <atom:updated>2026-11-04T14:00:48.161Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*aTmk2HhqL7RpyKAu.jpg" /></figure><p>In October 2026, a handful of Shopify apps had their settings changed by unauthorized people, and some shoppers who clicked Checkout were sent to a look-alike payment page before landing on the real one. The reassuring part is that the check takes about five minutes, and the apps involved responded quickly. Here is what is known so far, how to test your own store, and a few habits that keep it tidy.</p><h3>What happened</h3><p>On October 10, developer Roman Zipp was shopping on an online store when the checkout page asked his password manager for card details in the wrong field. He looked at the address bar, saw an unfamiliar domain, and traced the redirect back to an app called Hulk Product Options.</p><p>In the days that followed, Selleasy and Swym Wishlist Plus each described incidents of their own, and merchants reported a few more apps, some of which are still unconfirmed. Each vendor said unauthorized changes had added storefront code. Shopify has not said that its own checkout was breached. As far as the public record shows, the entry point was the app settings, not the store theme.</p><h3>How the redirect worked</h3><p>Many Shopify apps let a merchant add custom JavaScript or custom labels in the app’s own dashboard. The app’s storefront code then asks the vendor’s server for those settings every time a page loads, and runs what comes back.</p><p>In the Hulk case, Zipp found roughly 22.7 KB of JavaScript inside that response. The script waited for a click on Checkout, sent the shopper to a look-alike page, and then forwarded them to the real checkout, so the order still went through. It only ran once per browser session, which is why store owners testing their own site often saw nothing unusual.</p><p>Because the code arrived from the vendor’s server, the theme files themselves looked clean. That is the main reason a quick theme scan can miss it.</p><h3>Test your checkout in five minutes</h3><ol><li>Open a fresh private browser window.</li><li>Add any product to the cart.</li><li>Click Checkout and read the address bar. You should be on your own domain or Shopify’s checkout, nothing else.</li><li>Repeat in a second private window and once on your phone. The script ran once per session, so one clean test is not the full picture.</li><li>Clear the browser’s site data between tests, since app settings can be cached.</li></ol><p>If you land on an unfamiliar domain, especially one ending in .top, stop there and see the section below.</p><h3>Review your installed apps</h3><p>Open Settings, then Apps and sales channels, and go through the list.</p><ul><li>Remove apps nobody uses. Fewer apps means fewer places for code to live.</li><li>For each app that touches the storefront, open its own dashboard and look for Custom JavaScript or Custom HTML fields. Clear anything you did not add yourself.</li><li>In the theme editor, open App embeds and switch off the ones you do not need.</li><li>Remove old staff and contractor accounts.</li><li>Turn on two-step sign-in for Shopify, the email behind it, and every app account that offers it.</li></ul><h3>What Shopify and the vendors did</h3><p>Shopify’s changelog on October 20 announced that online stores now ask customers to confirm before sending them to a website outside the store. Shopify also published guidance for app developers called Securing your app, together, asking for two-step sign-in, expiring access tokens and regular endpoint scans.</p><p>The vendors moved quickly too. HulkApps removed the unauthorized code and hired an independent security firm. Selleasy said it fixed the cause within hours and later passed Shopify’s security checks and returned to the App Store. Swym paused its app for all merchants while it added protections. These are the companies’ own statements, so it is sensible to read each vendor’s incident page before reinstalling or re-enabling an app.</p><h3>If you spot an unfamiliar page</h3><ol><li>Do not enter card details.</li><li>Note the full address and the time, and take a screenshot of the address bar.</li><li>Contact Shopify Support and the developer of any app you recently installed or updated.</li><li>Change your Shopify and app passwords, and turn on two-step sign-in.</li><li>If a shopper typed a card number into the page, they should contact their card issuer.</li></ol><h3>A simple monthly habit</h3><ul><li>Weekly: run the private-window checkout test from two devices.</li><li>Monthly: review installed apps and their custom-code fields.</li><li>Quarterly: remove old staff access and review sign-in settings.</li><li>Before installing a new app: read the permissions it asks for and who can change its code.</li></ul><p>A calm, regular check like this catches most surprises early. If you would like a second pair of eyes on your store or hosting, I am happy to help at <a href="https://expertwebdeveloper.in/">expertwebdeveloper.in</a> and <a href="https://growsmartwithai.com/">growsmartwithai.com</a>.</p><h3>Sources</h3><ul><li>Roman Zipp, <a href="https://romanzipp.com/blog/shopify-hit-with-phishing-attack">Shopify shops hit with ongoing Checkout Hijack attack</a></li><li>Ecomistryy, <a href="https://ecomistryy.com/blog/shopify-checkout-hijack-how-to-check-your-store/">Shopify Checkout Hijack: How to Check Your Store</a></li><li>Appziot, <a href="https://www.appziot.com/blogs/shopify-checkout-security-third-party-apps-2026/">Shopify Checkout Security in 2026</a></li><li>Text Connects, <a href="https://textconnects.com/blogs/news/shopify-checkout-hijack-update-october-2026">Shopify Checkout Hijack Update</a></li><li>Shopify changelog, <a href="https://changelog.shopify.com/posts/new-protection-against-unexpected-redirects">New protection against unexpected redirects</a></li></ul><p>Also published on dev.to: <a href="https://dev.to/vijay_mishra_14dd027a16ee/shopify-checkout-redirect-how-to-check-your-store-and-your-apps-cf3">Shopify Checkout Redirect: How to Check Your Store and Your Apps</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9692a7e8d7d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[PHP2Shell: How to Check Your Website for the Critical PHP Flaw]]></title>
            <link>https://medium.com/@vijaysuper11/php2shell-how-to-check-your-website-for-the-critical-php-flaw-b02a51e8275b?source=rss-4dea5301688c------2</link>
            <guid isPermaLink="false">https://medium.com/p/b02a51e8275b</guid>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Vijay Mishra]]></dc:creator>
            <pubDate>Tue, 03 Nov 2026 12:49:31 GMT</pubDate>
            <atom:updated>2026-11-03T12:55:23.086Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5UIFOkzFB4cAIYw6.jpg" /></figure><p>If your website runs on PHP, which includes almost every WordPress site, there is one update to confirm with your host this week. On October 21, 2026, the PHP project released fixes for two serious flaws, CVE-2026–109618 and CVE-2026–109619, nicknamed PHP2Shell. Both can let an attacker run code on a server without logging in, and attacks have been reported. The good news is that the fix is a normal PHP update, and your host probably handles it. This post explains what happened and gives you a short list of things to ask and check.</p><h3>What happened</h3><p>PHP released new versions on October 21 that fix two related bugs in how the server handles web requests. In plain terms, the first one can leave a request half built when the server runs out of memory, and the clean-up code then trusts it. The second lets data from one request survive after its memory is freed, and a later request on the same worker can read it. In both cases the result can be remote code execution. Each scores 9.2 on the CVSS 4.0 scale.</p><p>Security researchers at watchTowr said they saw exploitation from October 21, and CISA added CVE-2026–109618 to its list of known exploited vulnerabilities. Cloudflare has also reported attack traffic aimed at the flaws, and public proof-of-concept scripts exist. The software that serves PHP matters here: Apache with mod_php carries the highest risk, though PHP-FPM, LiteSpeed and others are also in scope.</p><h3>Which versions are fixed</h3><p>The fixed releases are:</p><ul><li>PHP 8.5.12</li><li>PHP 8.4.27</li><li>PHP 8.3.36</li><li>PHP 8.2.35</li></ul><p>Anything newer than these is also fine. PHP 8.1 and older no longer get regular security updates from the PHP project. The project did publish limited source backports for 7.4, 8.0 and 8.1, and many hosts and Linux distributions ship their own patched packages. That means your version number can look old and still include the fix. Your host can confirm.</p><p>One useful point from the WordPress side: this is a server issue, so updating WordPress or plugins does not fix it. The WordPress security team has said no WordPress update is needed.</p><h3>Check 1: Find your PHP version</h3><p>In WordPress, open Tools, then Site Health, then the Info tab, and look under Server. Otherwise, check your hosting control panel. Write the version down for every site you run, including old ones and test sites.</p><h3>Check 2: Ask your host three plain questions</h3><p>Ask which PHP version is running, whether it includes the fixes for the two CVEs, and when the fix was applied. Also ask whether PHP and the web server were restarted afterward. Running processes keep the old code in memory until they restart, so a patch without a restart is not finished.</p><h3>Check 3: Upgrade if you are on an old branch</h3><p>If you are on PHP 8.1 or older and your host has no patched package, plan an upgrade to a supported branch. PHP 8.3 or newer is a sensible target. PHP 8.2 reaches the end of its support on December 31, 2026, so many people are choosing to skip it. Test your plugins and theme on a staging copy first, since a jump of several versions can break older code.</p><h3>Check 4: Keep a temporary setting in place</h3><p>Upgrades take time, and the PHP project suggests a few interim steps. One is switching off session upload progress, with the setting session.upload_progress.enabled=0, then restarting the workers. It reduces exposure to one of the flaws. PHP is clear that no configuration change fully fixes these bugs, so treat it as a short-term measure.</p><h3>Check 5: Look for signs of trouble</h3><p>Early attempts may date back to around October 17. Look for admin users you do not recognize, unfamiliar files, new scheduled tasks, and unexplained crashes or restarts of your web server. If anything looks odd, change passwords and keys, starting with hosting and admin accounts, and turn on multi-factor authentication.</p><h3>Check 6: Be careful with offers of help</h3><p>Every big security story brings a wave of messages offering a quick fix. Do not install a “PHP2Shell fix” plugin or paste code from a forum or social post. Contact your host through its official website or phone number instead.</p><h3>A short checklist</h3><ul><li>PHP version noted for every site</li><li>Host confirms the fixed version or a backported package</li><li>PHP and web server restarted after the update</li><li>Plan in place if you are on PHP 8.1 or older</li><li>session.upload_progress.enabled set to 0 until you are patched</li><li>Admin users, files and scheduled tasks reviewed</li><li>Passwords changed and multi-factor authentication on</li></ul><h3>Why this one is a quiet job</h3><p>Most of this work happens on your host’s side, so the main job is asking and getting an answer in writing. If you run a business site, a short message to your hosting provider today is a good use of five minutes. For more practical website guides, visit <a href="https://expertwebdeveloper.in/">expertwebdeveloper.in</a> and <a href="https://growsmartwithai.com/">growsmartwithai.com</a>.</p><h3>Sources</h3><ul><li>Qualys: <a href="https://blog.qualys.com/vulnerabilities-threat-research/2026/10/20/php-announces-critical-security-release-for-two-vulnerabilities">PHP2Shell: Find, Mitigate, and Patch Now</a></li><li>watchTowr: <a href="https://watchtowr.com/intelligence/php-cve-2026-109618-faq/">CVE-2026–109618: Exploited Remote Code Execution in PHP</a></li><li>U.S. Chamber of Commerce: <a href="https://www.uschamber.com/co/run/technology/php-security-flaw-small-business-guide">A Security Flaw Is Affecting Millions of Websites: What Small Business Owners Need to Do</a></li><li>NCSC-NL: <a href="https://github.com/NCSC-NL/php2shell">Operational information regarding the 2026 php2shell vulnerabilities</a></li></ul><h3>Also published on</h3><ul><li><a href="https://dev.to/vijay_mishra_14dd027a16ee/php2shell-how-to-check-your-website-for-the-critical-php-flaw-4dea">dev.to</a></li></ul><p>Also available on <a href="https://iamvijaymishra.substack.com/p/php2shell-how-to-check-your-website">Substack</a>, <a href="https://expertwebdeveloper.in/blog/php2shell-php-vulnerability-website-check/">expertwebdeveloper.in</a>, <a href="https://growsmartwithai.com/blog/php2shell-php-vulnerability-website-check/">growsmartwithai.com</a> and <a href="https://www.linkedin.com/pulse/php2shell-how-check-your-website-critical-php-flaw-vijay-mishra-baw7c/">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b02a51e8275b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Node.js Brotli Vulnerability (CVE-2026–111497): What to Check on Your Servers]]></title>
            <link>https://medium.com/@vijaysuper11/node-js-brotli-vulnerability-cve-2026-111497-what-to-check-on-your-servers-6541492e5a65?source=rss-4dea5301688c------2</link>
            <guid isPermaLink="false">https://medium.com/p/6541492e5a65</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Vijay Mishra]]></dc:creator>
            <pubDate>Mon, 02 Nov 2026 07:59:28 GMT</pubDate>
            <atom:updated>2026-11-02T11:02:55.635Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9xzRqdAT-WBsN8um.jpg" /></figure><p>If your website, shop or app runs on Node.js, one update deserves your attention this week. On October 21, 2026, the Node.js team released security versions that fix a serious flaw in Brotli, the compression library behind many “br” responses on the web. The flaw is tracked as CVE-2026–111497, and it has already been added to the US CISA list of known exploited vulnerabilities. The fix is a normal update. This post explains what is affected and gives you a short list to work through.</p><h3>What happened</h3><p>Brotli is a compression format created by Google. Browsers, servers and many programming tools use it to shrink data. CVE-2026–111497 is an out-of-bounds write in the Brotli decoder, the part that unpacks compressed data. If an application decompresses Brotli data that an attacker controls, the result can be a crash, a leak of memory contents or, in the worst case, running the attacker’s code.</p><p>The score is high. Google’s CVSS 4.0 rating is 9.2, and the NVD CVSS 3.1 rating is 9.8. Some write-ups call it Node2Shell. A public proof of concept exists, and security researchers have reported exploit traffic aimed at Node.js servers. Reports describe the observed attempts crashing the process rather than taking over the machine, but nobody should wait to see how that develops.</p><h3>Which versions are affected</h3><p>Node.js fixed the problem in these releases:</p><ul><li>Node.js 22.23.4</li><li>Node.js 24.22.1</li><li>Node.js 26.12.1</li></ul><p>Older builds on those three lines are affected. The end-of-life lines, 20.x, 23.x and 25.x, are also affected and will not get a fix, so they need to move to a supported version.</p><p>The Brotli library itself is fixed in 1.0.10, 1.1.1 and 1.2.1. Other software that bundles Brotli has its own updates. Tenable lists .NET, Bun, Envoy Proxy, Istio, FFmpeg, Apache Arrow and ClickHouse as products to review, and Python’s brotli packages have fixed versions too. If you are unsure whether you use any of these, ask your host or developer.</p><h3>Check 1: Find out where Node.js runs for you</h3><p>Node.js is easy to forget. It may power your main app, but it also hides in build tools, API servers, headless front ends, scheduled jobs and CI runners. Make a short list of every place it runs. A standard WordPress site on PHP is not running Node.js for its pages, but the tools around it sometimes are.</p><h3>Check 2: Update to a fixed release</h3><p>Run node --version on each machine and compare it to the fixed versions above. If you are behind, update to the latest release on your line, then restart the service. On a managed host, check whether your hosting panel lets you choose the Node.js version and pick the newest patch of a supported line.</p><h3>Check 3: Do not forget containers and build images</h3><p>An updated server does not help if your container image still has the old runtime inside. Rebuild images from a fresh base, redeploy, and check the version on the running workload, not only in your build files. The same goes for CI runners and any bundled Node.js binary inside a desktop or command-line tool you ship.</p><h3>Check 4: Updating packages is not the same as updating Node.js</h3><p>One point from the technical write-ups is worth repeating: upgrading npm packages such as Express does not fix this flaw. Only a patched Node.js release does. Keep that in mind if your dependency tool shows everything as up to date.</p><h3>Check 5: Limit untrusted Brotli input until you are patched</h3><p>If you cannot update right away, you can reduce exposure. The risk depends on whether your app decompresses Brotli data from people you do not trust, such as request bodies or responses fetched from outside services. For incoming request bodies, the body-parser option inflate: false helps, though it does not cover responses your server fetches itself. A web application firewall rule can buy a little time, but treat it as a stopgap only.</p><h3>Check 6: Look back at what was exposed</h3><p>If an internet-facing Node.js service accepted compressed request bodies before you patched, look through your logs for crashes and restarts around late October. A sudden process crash on a service that was stable before is worth a second look.</p><h3>A short checklist</h3><ul><li>Every place Node.js runs is listed</li><li>Each one is on 22.23.4, 24.22.1, 26.12.1 or newer</li><li>End-of-life versions (20.x, 23.x, 25.x) are scheduled for an upgrade</li><li>Containers and CI images rebuilt and redeployed</li><li>Services restarted and the running version confirmed</li><li>Other Brotli users (.NET, Bun, Python packages) reviewed</li><li>Logs checked for unexplained crashes</li></ul><h3>Why this one matters</h3><p>Compression bugs are a good reminder that the quiet parts of a stack matter as much as the visible ones. Nothing here asks for a rebuild of your site. It asks for one tidy afternoon: find the runtimes, update them, restart them and confirm the version. CISA gave US federal agencies until November 10 to finish their fixes, which is a sensible deadline for everyone else to aim for as well.</p><p>For more practical website guides, visit <a href="https://expertwebdeveloper.in/">expertwebdeveloper.in</a> and <a href="https://growsmartwithai.com/">growsmartwithai.com</a>.</p><h3>Sources</h3><ul><li>Cyber Security Agency of Singapore: <a href="https://www.csa.gov.sg/alerts-and-advisories/alerts/al-2026-154/">Active Exploitation of Critical Brotli Vulnerability Affecting Multiple Products</a></li><li>Tenable: <a href="https://www.tenable.com/cve/CVE-2026-111497">CVE-2026–111497</a></li><li>Help Net Security: <a href="https://www.helpnetsecurity.com/?p=389353">Brotli bug reaches far beyond Node.js (CVE-2026–111497)</a></li><li>Rescana: <a href="https://www.rescana.com/post/nodejs-cve-2026-111497-node2shell-brotli-rce-october-2026">Node.js CVE-2026–111497 Node2Shell Brotli RCE, October 2026</a></li></ul><h3>Also published on</h3><ul><li><a href="https://dev.to/vijay_mishra_14dd027a16ee/nodejs-brotli-vulnerability-cve-2026-111497-what-to-check-on-your-servers-bih">dev.to</a></li><li><a href="https://iamvijaymishra.substack.com/p/nodejs-brotli-vulnerability-cve-2026">Substack</a></li><li><a href="https://expertwebdeveloper.in/blog/nodejs-brotli-vulnerability-cve-2026-111497/">expertwebdeveloper.in</a></li><li><a href="https://growsmartwithai.com/blog/nodejs-brotli-vulnerability-cve-2026-111497/">growsmartwithai.com</a></li><li><a href="https://www.linkedin.com/pulse/nodejs-brotli-vulnerability-cve-2026-111497-what-check-vijay-mishra-waltc/">LinkedIn</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6541492e5a65" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chrome HTTPS Warning: A Quick Audit for Your Website]]></title>
            <link>https://medium.com/@vijaysuper11/chrome-https-warning-a-quick-audit-for-your-website-0be4c64554f7?source=rss-4dea5301688c------2</link>
            <guid isPermaLink="false">https://medium.com/p/0be4c64554f7</guid>
            <category><![CDATA[https]]></category>
            <dc:creator><![CDATA[Vijay Mishra]]></dc:creator>
            <pubDate>Sat, 31 Oct 2026 12:14:16 GMT</pubDate>
            <atom:updated>2026-11-02T11:03:32.152Z</atom:updated>
            <content:encoded><![CDATA[<p>If your website still has a few old pages or forgotten subdomains that load over plain HTTP, Chrome is about to make them more noticeable. Chrome is turning on its “Always Use Secure Connections” setting by default, which means visitors will be asked for permission before Chrome opens a public site that does not support HTTPS. The change is gentle and the fix is usually small. This post explains what is happening and gives you a one-evening checklist.</p><h3>What is changing in Chrome</h3><p>Chrome has long offered a setting called Always Use Secure Connections. When it is on, Chrome tries HTTPS first and, if a public site has no HTTPS version, shows a warning that the visitor can choose to bypass.</p><p>Google’s Chrome Security team announced the plan in October 2025:</p><ul><li><strong>Chrome 147 (April 2026):</strong> the setting switched on for people using Enhanced Safe Browsing, which Google said covers more than a billion users.</li><li><strong>Chrome 154 (October 2026):</strong> the setting switched on by default for everyone, in its “public sites” form.</li></ul><p>There is one detail where sources differ. Google’s original plan named Chrome 154. A later report on Chrome Enterprise release notes points to Chrome 155 for the default-for-all-users step, and also notes that a new Chrome build rolls out gradually over days and weeks. Because the exact build is not settled in what I could verify, the safest reading is simple: it is arriving about now, so check your site now.</p><h3>Who will actually see the warning</h3><p>Google’s own testing is reassuring. In an experiment in Chrome 141, warnings appeared on well under 3 percent of navigations, and the typical user saw fewer than one a week. Chrome does not keep warning about sites a person visits regularly. The prompt mostly appears for new or rarely visited pages.</p><p>Private addresses are left out. Things like a home router page, a single-word internal hostname or a company intranet link do not trigger it. Google also estimated that 1 to 5 percent of web traffic could be affected overall.</p><p>For a business site, the risk is not the main homepage. It is the long tail: an old campaign page, a regional subdomain, a documentation host or a download link that nobody has looked at in years.</p><h3>Check 1: List every public hostname you own</h3><p>Write down your main domain, every subdomain, and any older domains that still point somewhere. Include campaign sites, staging sites that were left public, and landing pages from past projects. Open each one with https:// in front and see whether it loads without a certificate error.</p><h3>Check 2: Make sure old hostnames have working HTTPS</h3><p>If an old hostname only redirects over HTTP, Chrome may show the prompt before the redirect is reached. The hostname itself needs a valid certificate, even if its only job is to send people to your main site. Most hosts give free certificates, so this is often a few clicks.</p><h3>Check 3: Look for mixed content</h3><p>On pages that are served over HTTPS, scan for images, scripts, stylesheets, iframes, videos or downloads that still use http:// addresses. Older blog posts are the usual culprits. A search-and-replace in your database or a plugin that fixes URLs can clear most of them.</p><h3>Check 4: Confirm certificates and renewals</h3><p>For each hostname, confirm the certificate covers it, the chain is valid and the expiry date is not close. Then check that automatic renewal is actually switched on. A certificate that quietly expires puts a site back in front of the same warning.</p><h3>Check 5: Update links you have shared elsewhere</h3><p>QR codes on printed material, email templates, partner links, social profiles and documentation often carry old http:// addresses. Writing http:// in a link does not trigger the prompt on its own when the hostname supports HTTPS, but updating them avoids an extra redirect and keeps things tidy.</p><h3>Check 6: Test it yourself</h3><p>You can try the behavior today. In Chrome, open chrome://settings/security and turn on Always use secure connections, then visit your key pages. If you manage computers for a team, Google documents an HttpsOnlyMode policy and an HttpAllowlist for hostnames that cannot move to HTTPS yet.</p><h3>A short checklist</h3><ul><li>All public hostnames listed</li><li>HTTPS loads cleanly on each one</li><li>Old hostnames have their own certificate</li><li>Mixed content cleaned up</li><li>Certificate renewal automated</li><li>Old http:// links updated</li><li>Key pages tested with the Chrome setting on</li></ul><h3>The bigger picture</h3><p>Public sites on HTTPS are already the norm. Google’s numbers put it at roughly 98 percent on Windows and above 99 percent on Mac and Android when only public sites are counted. This change is mostly about the last few stragglers, and for most site owners it is a small tidy-up rather than a project. For more practical website guides, visit <a href="https://expertwebdeveloper.in/">expertwebdeveloper.in</a> and <a href="https://growsmartwithai.com/">growsmartwithai.com</a>.</p><h3>Sources</h3><ul><li>Infosecurity Magazine: <a href="https://www.infosecurity-magazine.com/news/chrome-https-mandatory-2026/">Chrome to Make HTTPS Mandatory by Default in 2026</a></li><li>PPC Land: <a href="https://ppc.land/chrome-enforces-secure-connections-by-default-in-october-2026/">Chrome enforces secure connections by default in October 2026</a></li><li>Semonto: <a href="https://semonto.com/blog/chrome-154-will-ask-before-http">Chrome 154 will ask before HTTP: audit your forgotten URLs now</a></li><li>WindowsForum: <a href="https://windowsforum.com/news/chrome-154-or-155-when-https-first-warnings-become-default-and-how-to-manage-them.447078/">Chrome 154 or 155: when HTTPS-first warnings become default</a></li></ul><p>Also published on <a href="https://dev.to/vijay_mishra_14dd027a16ee/chrome-https-warning-a-quick-audit-for-your-website-4gn1">dev.to</a>.</p><p>Also available on <a href="https://iamvijaymishra.substack.com/p/chrome-https-warning-a-quick-audit">Substack</a>, <a href="https://expertwebdeveloper.in/blog/chrome-https-warning-website-audit/">expertwebdeveloper.in</a>, <a href="https://growsmartwithai.com/blog/chrome-https-warning-website-audit/">growsmartwithai.com</a> and <a href="https://www.linkedin.com/pulse/chrome-https-warning-quick-audit-your-website-vijay-mishra-obwcc/">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0be4c64554f7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Google AI Mode and Your Website: What to Check in Search Console]]></title>
            <link>https://medium.com/@vijaysuper11/google-ai-mode-and-your-website-what-to-check-in-search-console-d52917efa49b?source=rss-4dea5301688c------2</link>
            <guid isPermaLink="false">https://medium.com/p/d52917efa49b</guid>
            <category><![CDATA[seo]]></category>
            <dc:creator><![CDATA[Vijay Mishra]]></dc:creator>
            <pubDate>Fri, 30 Oct 2026 10:02:53 GMT</pubDate>
            <atom:updated>2026-11-02T11:03:56.271Z</atom:updated>
            <content:encoded><![CDATA[<p>If you own a website, you have probably heard that Google AI Mode is changing how people find businesses. The good news is that you do not need a new toolkit to respond. You need to look at a few settings and one report that Google now gives every site owner. This post walks through what changed recently, what Google itself says about showing up, and a short list of things you can check this week.</p><h3>What changed recently</h3><p>Google AI Mode is a conversational search experience. A person asks a question, gets a written answer with links to web pages, and can keep asking follow-ups. AI Overviews are a related feature, a short AI summary that can appear on a normal results page.</p><p>Three recent updates are worth knowing about:</p><ul><li><strong>August 31, 2026:</strong> Google rolled out the Generative AI performance report in Search Console to all websites worldwide. Before that, only some sites could see it.</li><li><strong>October 15, 2026:</strong> Google announced that links to sources would appear higher and more often inside AI Overviews and AI Mode, along with larger article carousels and a test of clickable publisher and creator names. Some of these are launching and some are still being tested, and Google did not share click data with the announcement.</li><li><strong>Late September 2026:</strong> Search Console added a multimodal filter, so you can separate visits that start from an image, such as Google Lens or Circle to Search, from ordinary text searches.</li></ul><h3>What Google says about showing up in AI Mode</h3><p>Google’s own guide for site owners is refreshingly plain. Its position is that optimizing for AI search is still search engine optimization. There is no special sign-up, no special markup and no secret file.</p><p>To be eligible, a page needs to be indexed and allowed to appear in Google Search with a snippet. The site also needs to be included in the Search generative AI setting in Search Console, which is switched on by default.</p><p>Google also lists a few things you can skip. You do not need an llms.txt file for Google Search, you do not need to chop your pages into tiny pieces, and you do not need to rewrite your content in a special style for AI. Structured data is useful for rich results, but it is not required for AI features.</p><p>What Google says matters most is content that offers something only you can offer. Its example contrasts a generic list of tips with a first-hand story from a real project. Detail from your own experience is hard to copy, and that is the point.</p><h3>Check 1: Confirm your site is included</h3><p>Open Search Console and go to Settings, then Search generative AI. Make sure your property is set to be included. If someone changed this in the past, you may have been hiding your pages from these features without knowing it.</p><h3>Check 2: Open the Generative AI performance report</h3><p>In Search Console, look for the Generative AI performance report. It shows how many times links to your site appeared in AI Overviews and AI Mode. You can view it by page, country, date and device, and you can export the data.</p><p>Two things to keep in mind. The report shows impressions, not clicks or search queries, so it tells you which pages are being shown but not what people typed. And if you cannot find the report, Google says that usually means your site has not had enough impressions in these features yet, or that the site has been excluded.</p><h3>Check 3: Save a baseline</h3><p>Before you change anything, export the last 28 days of data and keep the file. In a few months you will want to compare. Without a starting point, it is hard to tell whether your work made a difference.</p><h3>Check 4: Look at the pages that are being shown</h3><p>Sort the report by page. The pages that already appear are the ones to improve first, because Google is already treating them as useful. Add current details, a clear date, a named author and specifics from your own work. If an important page, such as a main service page, is missing from the list, that page is a good candidate for a rewrite.</p><h3>Check 5: Make sure nothing is blocking you</h3><p>A few quiet settings can get in the way. Check that your robots.txt file allows crawling, and that your hosting or CDN layer is not blocking Googlebot. Also check that no page template carries a nosnippet tag or a very low max-snippet value that you did not intend. Keep important information such as prices and service areas as real text, not only inside images or PDFs.</p><h3>Check 6: Keep business details current</h3><p>Google notes that Merchant Center feeds and Google Business Profiles can help products and services appear in AI responses. If you sell locally or sell products online, confirm that your hours, address, phone number and product details are up to date.</p><h3>A short checklist</h3><ul><li>Search generative AI setting is set to include</li><li>Generative AI performance report opened and exported</li><li>Top pages by impressions listed</li><li>Main service pages reviewed for first-hand detail</li><li>robots.txt, hosting and snippet settings checked</li><li>Business Profile and product data updated</li></ul><h3>What we still do not know</h3><p>Google has not published how many clicks AI answers send to websites, and the report does not show queries. Nobody outside Google can promise a particular spot in an AI answer, so treat the report as a direction indicator, not a sales counter. Watch your calls, messages and form submissions alongside it.</p><p>The steady habit of publishing useful, first-hand content and keeping your site technically healthy is still the most reliable plan. For more practical guides like this, visit <a href="https://expertwebdeveloper.in/">expertwebdeveloper.in</a> and <a href="https://growsmartwithai.com/">growsmartwithai.com</a>.</p><h3>Sources</h3><ul><li>Google Search Central: <a href="https://developers.google.com/search/docs/fundamentals/ai-optimization-guide">Optimizing your website for generative AI features on Google Search</a></li><li>Search Console Help: <a href="https://support.google.com/webmasters/answer/16984139">Generative AI performance report</a></li><li>eSEOspace: <a href="https://eseospace.com/blog/google-ai-mode-explained/">Google AI Mode explained</a></li><li>ScallMe: <a href="https://scall.me/en/google-ai-mode-search-console-data/">Google AI Mode: new data in Search Console for small businesses</a></li><li>AskWatch: <a href="https://askwatch.ai/blog/google-announces-link-visibility-changes-ai-search">Google announces five link visibility changes in AI Search</a></li></ul><p>Also published on dev.to: <a href="https://dev.to/vijay_mishra_14dd027a16ee/google-ai-mode-and-your-website-what-to-check-in-search-console-402e">Google AI Mode and Your Website</a>.</p><p>Also available on <a href="https://iamvijaymishra.substack.com/p/google-ai-mode-and-your-website-what">Substack</a>, <a href="https://expertwebdeveloper.in/blog/google-ai-mode-search-console-check/">expertwebdeveloper.in</a>, <a href="https://growsmartwithai.com/blog/google-ai-mode-search-console-check/">growsmartwithai.com</a> and <a href="https://www.linkedin.com/pulse/google-ai-mode-your-website-what-check-search-console-vijay-mishra-xabtc/">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d52917efa49b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WordPress Backdoor That Rebuilds Itself: How to Clean It Properly]]></title>
            <link>https://medium.com/@vijaysuper11/wordpress-backdoor-that-rebuilds-itself-how-to-clean-it-properly-29cb66b6a607?source=rss-4dea5301688c------2</link>
            <guid isPermaLink="false">https://medium.com/p/29cb66b6a607</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[wordpress]]></category>
            <category><![CDATA[malware]]></category>
            <dc:creator><![CDATA[Vijay Mishra]]></dc:creator>
            <pubDate>Wed, 28 Oct 2026 20:46:11 GMT</pubDate>
            <atom:updated>2026-10-28T21:10:12.826Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0N4V-9ljy8KN6RDl.jpg" /></figure><p>If you have ever cleaned a hacked WordPress site, deleted the bad files and watched them come back the next day, this post is for you. Security firm Sucuri has described a backdoor, which it calls SC, that is built to do exactly that. The useful news is that the way to deal with it is clear, and a calm, ordered clean-up works.</p><p>My last posts covered a poisoned Python package and the PHP2Shell flaws. This one stays closer to home for anyone who runs a WordPress site.</p><h3>What Sucuri found</h3><p>Sucuri came across SC while working on incident-response cases in September 2026 and published its research on October 1. The headline feature is persistence. The malware keeps copies of itself in at least eight places across files, the database and, on compatible servers, shared memory. If one piece is deleted, the others quietly put it back.</p><p>According to the write-up, those places include:</p><ul><li>a .user.ini file that loads a PHP file before every other script</li><li>hidden PHP files inside wp-content</li><li>an encoded payload stored in the database</li><li>code injected into a theme’s functions.php</li><li>a must-use plugin, which runs on every request and does not show on the normal Plugins screen</li><li>a regular plugin</li><li>shared memory segments</li></ul><h3>What it can do</h3><p>Once it is running, the reported abilities are practical ones for an attacker: creating a hidden administrator account, injecting JavaScript into pages, running arbitrary PHP, and turning other plugins off or deleting them. It also hides itself from the plugins list and from update checks.</p><p>For instructions, it uses the Ethereum blockchain rather than a single server. That matters because there is no one domain to block or take down. It also means the fix has to happen on your site, not at the attacker’s end.</p><h3>How sites get infected</h3><p>This is worth being clear about: Sucuri did not say how SC first reaches a site. The usual routes for this kind of malware are vulnerable plugins or themes, weak admin passwords, compromised supply chains and insecure upload features, but none of these was confirmed as the route SC used. Because there is no single software flaw behind it, there is also no vendor patch to install. The defence is good housekeeping plus a thorough clean-up.</p><h3>Why deleting files is not enough</h3><p>Sucuri’s point is that cleaning one layer leaves enough behind for the rest to regenerate. If you clean every file on disk but leave the database payload, the next page load restores the files. So the clean-up has to remove all the layers together, and it should come before you change passwords and keys, otherwise the malware can simply capture the new ones.</p><h3>A calm clean-up plan</h3><p>This follows Sucuri’s guidance to review files, database, theme code, plugins and server memory in one pass, and borrows the ordering suggested in a clean-up guide from security vendor Monarx. If the site matters to your business, a professional incident responder is a good investment.</p><ol><li><strong>Contain.</strong> Put the site in maintenance mode or switch PHP off for it, take a full copy of files and database for evidence, and treat every logged-in admin session as untrusted.</li><li><strong>Find the loader.</strong> Check mu-plugins, .user.ini and .htaccess for auto_prepend_file lines you did not add, plus db.php, advanced-cache.php and your theme’s functions.php for code you do not recognise.</li><li><strong>Remove everything together.</strong> Delete the hidden files and injected blocks, the malicious plugin entries, and the stored payloads in the database options table. Restart PHP so nothing is served from memory.</li><li><strong>Check users.</strong> Look for administrator accounts you did not create, including ones that do not appear on the Users screen but exist in the database. Remove them and end all sessions.</li><li><strong>Check neighbours.</strong> On shared hosting, look at other sites in the same account for the same files.</li><li><strong>Then change secrets.</strong> Reset hosting, database and WordPress passwords and refresh the keys in wp-config.php only after the site is clean.</li><li><strong>Watch.</strong> Re-enable the site and check for returning files over the next few days.</li></ol><h3>Habits that make reinfection less likely</h3><ul><li>Keep core, plugins and themes updated, and remove anything you no longer use.</li><li>Avoid nulled or pirated plugins, which are a common hiding place for backdoors.</li><li>Use unique admin passwords with two-factor sign-in.</li><li>Limit who can write to wp-content, and consider turning off in-dashboard file editing.</li><li>Keep off-site backups from before any problem, so a restore is possible.</li><li>Add a file-integrity or malware scanning plugin, and read its alerts.</li></ul><h3>A short checklist for this week</h3><ol><li>List every plugin and theme on your sites and remove the unused ones.</li><li>Check the mu-plugins folder for files you do not recognise.</li><li>Look at your administrator list for names you did not add.</li><li>Turn on two-factor sign-in for every admin.</li><li>Confirm you have a recent off-site backup you can restore.</li></ol><p>Small, regular checks like these take minutes and make a real difference. If you would like a second pair of eyes on a WordPress site, you can find me at <a href="https://expertwebdeveloper.in/">expertwebdeveloper.in</a> and read more security notes at <a href="https://growsmartwithai.com/">growsmartwithai.com</a>.</p><p>This post is also available on <a href="https://dev.to/vijay_mishra_14dd027a16ee/wordpress-backdoor-that-rebuilds-itself-how-to-clean-it-properly-124b">dev.to</a>. Also on <a href="https://expertwebdeveloper.in/blog/wordpress-self-healing-backdoor-cleanup/">https://expertwebdeveloper.in/blog/wordpress-self-healing-backdoor-cleanup/</a> and <a href="https://growsmartwithai.com/blog/wordpress-self-healing-backdoor-cleanup/">https://growsmartwithai.com/blog/wordpress-self-healing-backdoor-cleanup/</a> and <a href="https://iamvijaymishra.substack.com/p/wordpress-backdoor-that-rebuilds">https://iamvijaymishra.substack.com/p/wordpress-backdoor-that-rebuilds</a> and <a href="https://www.linkedin.com/pulse/wordpress-backdoor-rebuilds-itself-how-clean-properly-vijay-mishra-kughc/">https://www.linkedin.com/pulse/wordpress-backdoor-rebuilds-itself-how-clean-properly-vijay-mishra-kughc/</a></p><p><strong>Sources:</strong> <a href="https://thehackernews.com/2026/10/wordpress-backdoor-rebuilds-itself.html">The Hacker News</a> · <a href="https://dailysecurityreview.com/cyber-security/self-healing-wordpress-backdoor-defies-standard-removal/">Daily Security Review</a> · <a href="https://www.monarx.com/press-news/the-wordpress-infection-that-rebuilds-itself-faster-than-you-can-delete-it">Monarx</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29cb66b6a607" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[LiteLLM Supply Chain Attack: What Happened and What Python Teams Should Do]]></title>
            <link>https://medium.com/@vijaysuper11/litellm-supply-chain-attack-what-happened-and-what-python-teams-should-do-cb0dc6676f87?source=rss-4dea5301688c------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb0dc6676f87</guid>
            <category><![CDATA[python]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Vijay Mishra]]></dc:creator>
            <pubDate>Tue, 27 Oct 2026 18:03:09 GMT</pubDate>
            <atom:updated>2026-10-27T18:12:13.028Z</atom:updated>
            <content:encoded><![CDATA[<p>If your team uses Python for anything AI related, there is a good chance LiteLLM is somewhere in your stack. It is a popular gateway that lets one codebase talk to many model providers. On October 21, a poisoned release of it spent about two hours on PyPI and Docker registries. This post explains what happened, who needs to act, and the habits that make the next incident a smaller one.</p><p>My recent posts covered PHP2Shell, the record Patch Tuesday, AI coding agents and the weekly web stack patches. This one is about a different kind of risk: the packages we install without a second thought.</p><h3>What happened</h3><p>The project’s release pipeline was compromised early on October 21, and a version labelled 1.107.0 was published to PyPI, Docker Hub and the GitHub container registry. LiteLLM says all earlier versions are safe, the bad releases have been pulled, and customers of its private enterprise registry were not affected.</p><p>One detail is worth knowing. The official 1.107.0 source tag on GitHub did not contain the malicious files. The packages were built from a lookalike repository, Berri-AI/litellm, which is one hyphen away from the real BerriAI/litellm. That is why reading the public source would not have caught it.</p><h3>Am I affected? The exact windows</h3><p>According to LiteLLM’s incident report, all times UTC on October 21:</p><ul><li>PyPI, litellm 1.107.0 (all seven wheels): live from 11:39 to 13:23.</li><li>Docker Hub tags v1.107.0, latest, main-latest and main-stable: pointed at the bad image from 11:46 to 14:20.</li><li>GitHub container registry tags: unavailable by 13:51.</li></ul><p>You are in the affected group if you ran pip install on an unpinned LiteLLM, or pulled one of those image tags, inside those windows. If you were pinned to an earlier version, you were not.</p><h3>What the malicious code did</h3><p>Researchers at Socket describe malicious files placed in Python startup locations, which means the code runs whenever Python starts in that environment, even if your application never imports LiteLLM. The reported targets included cloud credentials for AWS, Azure, Google Cloud, Kubernetes and Docker, plus Git credentials, SSH and GPG keys, browser data, and authentication files for several AI tools. The collected data was encrypted and sent to an outside address. A second component periodically checked for more code to run.</p><p>Wiz reported that about four and a half hours after the data left victim systems, the attacker started testing stolen AWS credentials, including whether they could reach AI models on Amazon Bedrock. So the keys were tried quickly, and rotation is the part that cannot wait.</p><h3>How the attackers got in</h3><p>LiteLLM first suspected one route, then corrected itself after finishing its investigation, and I am using the corrected account. In late May, a configuration file containing the master key for an experimental internal service was committed to a public repository. The commit was replaced, but that key was never revoked. On October 10 the attacker used it to read a GitHub token belonging to an organization owner. With that, they used the project’s own CI workflows to collect tokens from two maintainers. On October 21 they pointed the release workflow at the lookalike repository, approved the release with a stolen token and deleted the workflow records.</p><p>The lesson is a kind one for every team: an exposed key stays dangerous until it is rotated, and broad personal tokens in automation make a small leak much bigger. LiteLLM has said it is rotating every token across its systems and plans to share process changes.</p><h3>If you ran 1.107.0</h3><p>Please follow LiteLLM’s guidance, and do it from a shell rather than by running Python:</p><ol><li>Do not start with pip install. Any Python start in the affected environment runs the startup files again, and that includes pip.</li><li>Delete cook.pth, cook.py and sitecustomize.py (and their cached .pyc files) from every affected site-packages folder, and stop the background Python process that holds /tmp/remote_code_loader.lock.</li><li>Reinstall pinned to litellm 1.106.2, or better, rebuild images and virtual environments from scratch.</li><li>Assume the data left the machine if it had internet access. Finding the marker files confirms exposure, but not finding them proves nothing.</li><li>Rotate everything the host could reach: cloud roles, every provider key stored in the LiteLLM proxy database, the master and virtual keys, the database password, and any secret in a process environment.</li><li>In AWS CloudTrail, look for GetCallerIdentity calls from the instance role around install time, then for use of its credentials from outside your network.</li></ol><h3>Habits that shrink the blast radius</h3><ul><li>Pin exact versions in a lockfile, and use hash checking where your tooling supports it.</li><li>Pin container images by digest, not by tags such as latest. A tag is only as safe as the last push to it.</li><li>Give CI and automation scoped tokens from service accounts instead of a person’s own login.</li><li>Rotate keys the moment they appear anywhere public, even briefly.</li><li>Keep secrets out of long-lived environment variables where you can, so one compromised process sees less.</li></ul><h3>What this shows</h3><p>Trusted channels can carry bad code. The release came through the same registries teams use every day. AI gateways collect many keys in one place, which makes them attractive. And speed helped here: a community member opened a public issue within about half an hour of publication, and the registries removed the files within hours. Good habits make the difference between a close call and a clean-up.</p><h3>A short checklist for this week</h3><ol><li>Search your projects and images for litellm 1.107.0.</li><li>Confirm every LiteLLM install is pinned to 1.106.2 or an earlier explicit version.</li><li>If anything ran 1.107.0, isolate it, clean it and rotate its credentials.</li><li>Switch floating image tags to digests.</li><li>Review which tokens your CI uses and trim their scope.</li></ol><p>Calm, steady steps now save a long weekend later. If you want help reviewing a WordPress, Python or hosting setup, you can find me at <a href="https://expertwebdeveloper.in/">expertwebdeveloper.in</a> and read more security notes at <a href="https://growsmartwithai.com/">growsmartwithai.com</a>.</p><p><strong>This post is also available on </strong><a href="https://expertwebdeveloper.in/blog/litellm-supply-chain-attack-what-to-do/"><strong>https://expertwebdeveloper.in/blog/litellm-supply-chain-attack-what-to-do/</strong></a><strong> and </strong><a href="https://growsmartwithai.com/blog/litellm-supply-chain-attack-what-to-do/"><strong>https://growsmartwithai.com/blog/litellm-supply-chain-attack-what-to-do/</strong></a><strong> and </strong><a href="https://iamvijaymishra.substack.com/p/litellm-supply-chain-attack-what"><strong>https://iamvijaymishra.substack.com/p/litellm-supply-chain-attack-what</strong></a><strong> and </strong><a href="https://dev.to/vijay_mishra_14dd027a16ee/litellm-supply-chain-attack-what-happened-and-what-python-teams-should-do-50fa"><strong>https://dev.to/vijay_mishra_14dd027a16ee/litellm-supply-chain-attack-what-happened-and-what-python-teams-should-do-50fa</strong></a><strong> and </strong><a href="https://www.linkedin.com/pulse/litellm-supply-chain-attack-what-happened-python-teams-vijay-mishra-6d9gc/"><strong>https://www.linkedin.com/pulse/litellm-supply-chain-attack-what-happened-python-teams-vijay-mishra-6d9gc/</strong></a></p><p><strong>Sources:</strong> <a href="https://docs.litellm.ai/blog/security-incident-oct-21-2026">LiteLLM incident report</a> · <a href="https://docs.litellm.ai/blog/security-incident-oct-21-2026-attack-chain">LiteLLM attack chain write-up</a> · <a href="https://www.helpnetsecurity.com/2026/10/22/litellm-compromised-supply-chain-attack-pypi-docker/">Help Net Security</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb0dc6676f87" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>