❌

Normal view

phpAfterShell Explained: How Hackers Could Turn a PHP Session Flaw Into Code Execution

19 November 2026 at 16:59
PHP's default file-based session storage can be made to return objects an attacker chose, by cutting off a session write at the right moment. When combined with a second weakness, such as a suitable gadget chain in the app, those objects can allow the attacker to run code on the server. Today's PHP releases fix the flaw, called phpAfterShell. The flaw is tracked as CVE-2026-126714 and rated

PHP Fixes 7 Critical Flaws, Including Bugs That Could Allow Remote Code Execution

19 November 2026 at 15:18
The PHP Foundation has released security updates to address multiple critical security flaws that could be exploited to achieve remote code execution on affected deployments, including CVE-2026-115560. The release of the patch follows an advance notice in which the project maintainers alerted users to multiple critical vulnerabilities affecting all supported PHP versions under specific

Critical VMware vCenter Flaw (CVSS 9.8) Lets Network Attackers Bypass Authentication

19 November 2026 at 15:11
A critical flaw in VMware vCenter lets an attacker with network access bypass authentication and gain unauthorized access to the system, Broadcom, which owns VMware, said in an advisory published today. Fixed versions are out for all supported branches, and the company lists no workaround. vCenter is the central console for managing an organization's ESX hosts and virtual machines. The

Drupal Patches Critical Installer Flaw That Could Give Unauthenticated Attackers Control of Sites

19 November 2026 at 14:33
Under specific conditions, a critical vulnerability in Drupal core can allow an attacker without login credentials to use the built-in installer to attempt to reinstall a site. That can lead to a site takeover or remote code execution, and the project rates the vulnerable configurations as uncommon. Fixed releases for all supported branches shipped yesterday. The Drupal Security Team disclosed

Everything Is a Web Application, Including Your Firewall

19 November 2026 at 11:52
One of the early targets of PHP2Shell exploitation was the firewall. On October 28, Palo Alto Networks confirmed that attackers were exploiting the two PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619, against PAN-OS management interfaces exposed to the internet. Both flaws let anyone execute code on the web server without authentication. The disclosure itself went a little wrong.

Cyberattack on service provider exposes payee data at 40 Irish credit unions

19 November 2026 at 11:45
An attack on software provider Wellington IT exposed saved payee details held by around 40 Irish credit unions, prompting a minister to criticize the company's delay in notifying them. Robert Troy, Ireland's minister of state with responsibility for credit unions, said the breach happened in October but many affected institutions only learned of it in recent days. Troy told Irish broadcaster RTÉ that the breach occurred "sometime in October," and Wellington IT's delay in providing details to its credit union customers was "not acceptable." News of the issues affecting Irish credit unions broke on Tuesday, although the government said at the time it was only investigating a "possible cybersecurity incident" in the first instance, and did not name Wellington IT until Wednesday. Affected credit unions said attackers exploited a vulnerability in their provider's online banking platform between October 2 and 4. The flaw was closed on October 6. Troy said the affected credit unions were only informed for the first time in recent days. The exposed records concern payees saved in members' online banking accounts. Those records can also be linked to the members who created them. The information exposed varies between institutions and individual records, but disclosures list the following data types: Names on payee bank accounts and saved nicknames Business Identifier Codes (BICs) International Bank Account Numbers (IBANs) Sort codes Payment references Internal reference numbers that do not identify customers Payee addresses Credit unions including St. Canice's said online banking passwords, PINs, and login credentials were unaffected, and that the exposed payee details did not provide access to members' accounts or funds. St. Canice's warned members not to transfer money in response to anyone claiming it needed to be moved to safety because of the breach. The CEO of Belfast-based Wellington IT, Colin Mitchell, said in a statement that the company notified the affected organizations "as soon as we confirmed the potential risk to customer data." He said Wellington IT has engaged outside cybersecurity experts to help investigate the breach, and reported the matter to the relevant authorities. Mitchell added: "We are directly supporting our customers in their assessment of the potential impact on affected individuals and to help them meet any applicable regulatory obligations. "We recognize the importance of this matter to our customers and their members and are treating it with the utmost seriousness. We remain focused on completing a thorough investigation and communicating directly with our customers as the investigation progresses." Owned by Canadian company Vencora, Wellington IT has offices in Belfast and Dublin, and provides credit unions with software, mobile apps, private cloud infrastructure, and fully managed services. Around 40 credit unions in Ireland were affected, roughly a quarter of the national total, Troy said. Credit unions operate similarly to traditional banks, offering savings accounts and loans, but are owned by their members and are not-for-profit organizations. Troy told RTÉ that cybersecurity is a constant challenge for financial institutions, as technology and threats evolve over time. "What's most important is that financial institutions take all the right measures to mitigate against these threats and that is what is happening," he said. Separately, the UK's Financial Conduct Authority, Prudential Regulation Authority, and Bank of England opened a joint consultation on cyber resilience guidance on Thursday. The FCA said October brought its second-highest monthly tally of reported cyber incidents in five years, and the highest in 18 months. The proposed guidance clarifies how firms should meet existing requirements rather than introducing new rules. ®

TfL takes Oyster photocard website offline after attackers compromise customer accounts

19 November 2026 at 11:01
Transport for London (TfL) has copped to another cybersecurity breach, this time involving the account details of around 265,000 Oyster photocard customers. The capital's transport operator told The Register it first became aware something was amiss on November 16, when Oyster photocard customers started receiving emails asking them to create accounts they already had. The emails came from TfL's own systems, the transport body confirmed, but were generated as a result of the compromise. "We immediately took the TfL photocard website down while this was being investigated," said Shashi Verma, TfL's director of technology strategy and revenue. "The protection of personal information is a priority for us, and I apologize to our customers affected by this incident." TfL reckons its speedy response spared a considerable number of customers from having their details compromised. The transport operator says it has since contained the incident and contacted those potentially affected, though it is rather more forthcoming about what the hackers didn't get their hands on than what they did. TfL says no passwords, bank or payment card details, or customer journey information were compromised. It also believes the names and dates of birth of children with Zip Oyster cards were unaffected. Among those whose accounts may have been compromised are holders of Zip Oyster cards – issued to children as young as five – as well as students, apprentices, care leavers, veterans, and Londoners aged 60 and over. Despite the assurances about passwords, TfL says it will ask all photocard customers to change theirs, along with their security questions and answers. Those in the habit of recycling passwords across multiple websites are being advised to change them elsewhere, too. TfL says it has yet to find any evidence that the compromised data has been used and has notified the Information Commissioner's Office (ICO). The transport operator hasn't disclosed how the perpetrators got into its systems. Existing photocards will still let holders through the ticket barriers, though anyone needing to renew one or check their journey history will have to contact TfL's customer services team while the website is out of action. There's no word yet on when it'll be back. "We hope to restore the affected website services as quickly as possible," Verma said. TfL should be well versed in dealing with data breaches by now. In March, the transport operator told The Register it had notified more than 7 million customers following its September 2024 cyberattack. The hackers had accessed systems holding customers' names, email addresses, and home addresses, while around 5,000 customers were contacted as a priority because their bank account details may also have been compromised. Two teenagers were subsequently charged in connection with the attack, which authorities linked to the notorious Scattered Spider cybercrime crew. The ICO looked into that incident but opted not to take enforcement action against TfL, having deemed its response proportionate. There's nothing at present to suggest the two incidents are related. Londoners can at least rest assured that their Oyster photocards still work. Whether the information they handed over to obtain them is in someone else's hands is another matter. ®

Sticky note on monitor provided keys to the company’s kingdom

19 November 2026 at 10:15
Welcome, once again, to PWNED, where we talk smack about organizations that have smacked themselves down by practicing poor security hygiene. This week's story involves everyone's favorite low-tech password manager: the sticky note. Our terrifying tale comes courtesy of Christian Espinosa, a certified penetration tester with over 30 years of experience and the CEO of Blue Goat Cyber, a security company. Espinosa shared an experience where critical credentials were right out in the open for any person in the office to see. During a walkthrough of a client's office, he noticed a password written on a sticky note that was taped to an employee's monitor. While writing down your password and placing it in a physically secure paper notebook might be ok, taping it to the computer is definitely not. "Before I get my fingers on any system, I first walk the physical area that the system is located in — attackers do that when they're looking at a target too," Espinosa explained. “Physical security vulnerabilities are neglected much more often than technical security vulnerabilities and firms invest in firewalls where a sticky note is placed 3 feet from the front door." Espinosa took a photo of the sticky note and immediately tried logging into that employee's account. Success. Then, he tried the very same password on the VPN, which apparently had been maintained by that employee. Once he connected to the VPN, Espinosa had full access to the company network and all of its shared drives. He opened a shared drive that this employee had access to and there was an HR folder with all kinds of personally identifiable information (PII) about employees, including home addresses, driver's licenses, and scanned W-4 forms. There were even spreadsheets that listed everyone's salaries. The employee account also had access to a document that contained a list of internal server names and the names of the people in charge of each server (great for phishing). Another document had instructions for how to log into the accounting server specifically. The accounting server was a particular treasure trove of client information. On that server, Espinosa found a folder with vendor banking information, invoices, and payment records. "At that point, a password I had read from a sticky note during a walk-through had taken me from one desk to information that could have been used for payroll fraud, identity theft, or vendor-payment fraud," Espinosa said. After getting access to all this information, the pen tester presented his findings to the client. They quickly disabled the rogue account and started reviewing VPN access logs to see who else might have gotten into the network. They then searched the office to see if anyone else was exposing a password on a sticky note. Finally, they tightened permissions on the HR and accounting shares so that only people who really needed access to that data could get in. The lessons here are pretty obvious. Don't expose your passwords and, perhaps even more importantly, limit who has access to file shares that contain mission-critical data such as employee or client information. "The part that really got the client's attention was how easily the attack could have continued after I left the building," Espinosa posited. "Someone could have photographed that sticky note, walked out, connected to the VPN later that night, and started going through employee and financial records from somewhere else." ®

Hackers Breach N-able Cloud Server, Disrupting Email Security Management Across 3 Regions

19 November 2026 at 09:31
N-able on Wednesday disclosed that unknown threat actors gained unauthorized access to one of the servers in the Mail Assure and Spam Experts Hosted Cloud, causing it to disable management interfaces and APIs. "We have taken steps to mitigate the threat and are continuing to harden our services to reduce the risk of recurrence," N-able said. "The investigation is ongoing, but at this time we

Ruby Releases Fixes for 7 Regex and String Flaws, Warns 5 Have Proof-of-Concept RCE

19 November 2026 at 08:42
Ruby contains seven memory-safety flaws in its regular expression engine and its string case-conversion code. For five of them, its maintainers say, proof-of-concept exploits, or PoCs, have shown that crafted input can run code on the machine. "We are aware of PoCs that prove some of them can be used to trigger remote code execution," the maintainers said. The project released fixed versions

Researcher Demonstrates Database RCE Exploits Affecting PostgreSQL, MySQL and Oracle

19 November 2026 at 08:14
Low-privilege database accounts that cannot read a single application table can still be used to run code on the database server itself, a researcher has shown, by reaching memory-corruption bugs in the engine code behind ordinary SQL. The exploits, published yesterday, are the researcher's proofs of concept against PostgreSQL, MySQL and ClickHouse, plus a separate Oracle chain that needs no

CISA Warns of 4 Exploited Flaws Linked to Ransomware, Cryptomining, and LLMjacking Attacks

19 November 2026 at 08:00
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) on Wednesday added four vulnerabilities impacting Synology DiskStation Manager (DSM), BerriAI LiteLLM, Apache Axis, and Vanderbilt University Research Electronic Data Capture (REDCap) to its Known Exploited Vulnerabilities (KEV) catalog, citing evidence of active exploitation. The vulnerabilities are listed below -

PHP Warns of Critical Security Flaws Affecting All Supported Versions, Fixes Coming November 19

19 November 2026 at 04:33
The maintainers of the PHP programming language on Wednesday issued an advisory announcing an upcoming security release that addresses critical flaws. The release is scheduled for November 19, 2026, between 2 and 2:30 p.m. UTC. "These releases are part of PHP's regular four-week release cycle and will address security vulnerabilities affecting all supported PHP versions," the maintainers said.

Fastly Next-Gen WAF (Signal Sciences) agent fails open before rules load in Kubernetes sidecar deployments (vendor disputes; CVE pending)

19 November 2026 at 04:19

Posted by Zac Lohrenz on Nov 18

Fastly Next-Gen WAF (Signal Sciences) agent: fail-open before rules
load in Kubernetes sidecar deployments

Product: Fastly Next-Gen WAF agent (sigsci-agent) with the NGINX
module, Kubernetes sidecar deployment
Vendor: Fastly, Inc.
Affected: All agent versions in default configuration, through at
least 4.83.2 (tested 2026-11-12). Before 4.52.0 no
mitigation existed. 4.52.0 and later are affected...

Get ready for another critical PHP security release to drop

18 November 2026 at 22:38
Apologies in advance to all patch managers and security teams that thought they might get a break this week. The PHP Foundation will release a “critical” security update on Thursday between 14:00 and 14:30 UTC. While we don’t have many details about the latest vulnerabilities – these haven’t been leaked like last month’s critical PHP2Shell flaws – a Wednesday advisory said the highest-severity bugs in the upcoming release are rated critical. “The issues rated critical require either non-default configuration or uncommon setups,” the foundation said, urging PHP users to “prepare to upgrade promptly once the releases become available.” We do know that one of the vulnerabilities is another remote code execution (RCE) flaw, tracked as CVE-2026-115560. In October, the PHP Foundation told The Register that it had reserved this CVE identifier for another RCE bug, but added it would not get an emergency fix like the earlier two PHP2Shell vulnerabilities because the third one doesn't pose the same risk. CVE-2026-115560 “requires a very unlikely combination of configuration and specific PHP application code, which we do not expect to occur in practical use of PHP,” Elizabeth Barron, executive director of the PHP Foundation, told The Register at the time. “The issue can be mitigated with a configuration setting. So for the moment the PHP Security Team has only published an informational advisory on the PHP website, explaining exactly this situation.” The earlier informational advisory urged users to “set session.upload_progress.enabled=0 until the next regular bugfix release, to fully protect from an unlikely RCE vector.” These unlikely RCE attacks require an application to set “session.serialize_handler to php_binary or php_serialize in its configuration and then switch it to php at runtime with ini_set() before calling session_start().” Additionally, the session upload progress feature must be enabled, which the PHP Foundation said is very unlikely in real-world applications. The November security release follows a hectic October emergency PHP patch-a-thon, with security teams racing to apply fixes for CVE-2026-109618 and CVE-2026-109619, collectively called PHP2Shell, before attackers could abuse the memory-safety flaws in the open source programming language running on about 70 percent of websites. While it took miscreants longer to reverse engineer the PHP2Shell fixes than some researchers had anticipated – and the entire internet didn’t burn down in the meantime – the US Cybersecurity and Infrastructure Security Agency (CISA) did add the two PHP vulns to its Known Exploited Vulnerabilities catalog on October 26. Suspected Chinese attackers chained PHP2Shell with a Linux kernel privilege-escalation exploit to root 25 servers, including Palo Alto Networks firewalls linked to US government-affiliated organizations, as early as October 23, according to Dream researchers. The Israeli AI cybersecurity startup said the attackers targeted organizations across the US, Japan, Taiwan, and South Korea, and “likely still” have persistent, remote access to compromised organizations’ networks. ®

Optimizely Supply Chain Attack Hit Zoom, CNN, BBC: How to Protect Your Accounts

18 November 2026 at 22:20

Starting late on Nov. 15, 2026 (ET), an attacker slipped malicious JavaScript into the Optimizely Web Experimentation scripts of at least 178 organizations, including Zoom, the BBC, CNN, Salesforce, HSBC, and Equifax, according to a Nov. 16 analysis by Report URI. The code tried to swap cryptocurrency wallet addresses, skim payment cards typed into site forms, and deliver iPhone exploit kits to visitors. If you used an iPhone or entered card details on one of these sites during the attack, update iOS and review your card charges from Nov. 15 onward.

Optimizely confirmed the incident in a status page update posted at 01:02 UTC on Nov. 17 (8:02 p.m. ET on Nov. 16), saying it fixed the vulnerability and removed the injected code from affected projects.

How the Optimizely Supply Chain Attack Happened

The attacker didn’t break into Zoom, CNN, or the BBC directly. Instead, the attacker tampered with a third-party tool those sites load on every page, so each site served the malware to its own visitors.

What Is a Supply Chain Attack?

A supply chain attack is a cyberattack that compromises a trusted vendor or service so the attacker can reach that vendor’s customers, and those customers’ users, all at once. Instead of hacking 178 websites one by one, the attacker abused one shared service.

How the Code Got Onto Major Websites

  • The tool: Optimizely Web Experimentation lets companies test different versions of their web pages. Sites load a small Optimizely script, called a snippet, to run those tests.
  • The way in: Optimizely spokesperson Victoria Johnson told Gizmodo that an unauthorized party “exploited a vulnerability in the Experimentation account signup flow.”
  • The injection: Report URI found the attacker wrote code into each project’s “Project JavaScript,” a field that runs on every page. The snippet was still served from Optimizely’s own network, so it looked legitimate to the sites loading it.
  • The scale: Report URI checked 1,611 Optimizely snippets and found malicious code in 188 of them, belonging to 178 organizations. Banking and finance was the largest group, with 32 organizations.
  • The window: Report URI first saw the injected code on the BBC’s site at 11:21 p.m. ET on Nov. 15. Most infected snippets were cleaned between about 3:40 and 4:10 p.m. ET on Nov. 16, and by 4:52 p.m. only one of the 188 was still infected.

Optimizely wasn’t the only channel. Researchers also found tampered scripts from three smaller web services loading code tied to the same attacker infrastructure, with the earliest recorded on Nov. 13.

What the Malicious Code Did

Payload What It Targeted Key Details
Crypto address swapping Wallet addresses on the page, in forms, links, images, and the clipboard Covered Bitcoin, Ethereum and EVM chains, TRON, Solana, TON, Litecoin, Bitcoin Cash, and Dogecoin
Card skimming Card number, expiration date, and CVV submitted through a site’s own forms Added at 8:43 a.m. ET on Nov. 16; could not read card fields hosted by a separate payment processor
Cookie and screenshot theft Some browser cookies (those not marked HttpOnly) and a screenshot of the page Triggered when a swapped address appeared next to wallet or payment wording
iPhone exploit kits iPhones and iPads Coruna for iOS 13 to 17, DarkSword for iOS 18; iOS 26 devices were only fingerprinted. Between 12:13 and 12:57 p.m. ET on Nov. 16, delivery expanded to every visit from iOS 18.6 or earlier

 

Report URI said the attacker’s crypto wallets received about $7,040 within roughly nine hours on Nov. 16. Researchers can’t yet say how many cards were skimmed or how many iPhones were infected, Report URI’s Scott Helme told The Record.

Which Websites Were Affected by the Optimizely Hack?

Report URI’s list includes Zoom, the BBC, CNN, Salesforce, GitLab, IKEA, HSBC, Equifax, Air France-KLM, Ledger, and Peacock. The list also named Fox News, NPR, the ASPCA, and Invisalign. Optimizely’s own website and login page carried the code, too.

Being on the list doesn’t mean the company’s own servers were breached or that every visitor was infected. It means a third-party script on that company’s site was serving malicious code during the attack window. Report URI’s full list of affected organizations shows which specific domains were involved.

Are Breach Notices Going Out?

Optimizely says it has contacted affected business customers directly. “The vulnerable path is blocked, the injected code was removed, and customers have been contacted directly,” the company said in a statement reported by The Record.

As of Nov. 17, we have not found consumer breach notices or regulatory filings from the named organizations. Salesforce told Reuters it was investigating unauthorized changes to Optimizely scripts and had disabled them as a precaution, according to Help Net Security. Report URI has advised site owners to treat cards entered through their own forms on Nov. 16 as potentially exposed and to consider notifying customers, so notices may follow.

Watch out for scammers sending fake “breach notices” about this attack. A real notice won’t ask you to confirm your full card number, CVV, password, or seed phrase by email, text, or a link. If you get a notice, contact the company through its official website or the number on the back of your card.

Warning Signs You May Have Been Affected

Only people who visited an affected site during the attack window were exposed, and exposure doesn’t mean data was stolen. Watch for these signs:

Warning Sign Why It Matters
A crypto address you pasted or scanned doesn’t match the one you copied The code swapped wallet addresses for the attacker’s
Charges you don’t recognize after Nov. 15 The skimmer captured card details typed into some sites’ own checkout forms
A web page on an older iPhone kept reloading about every 60 seconds Report URI found the code reloaded pages every 60 seconds on iOS 18.6 or earlier
You were signed out unexpectedly, or see sign-ins you don’t recognize The code could steal some cookies that keep you signed in
An email or text about this “breach” asks for card, password, or wallet details Scammers use breach news as bait for phishing

How to Protect Yourself From the Optimizely Malware

  1. Update your iPhone and iPad now. Go to Settings > General > Software Update and install the latest version your device supports. The exploit kits in this attack target older iOS versions; the kit’s own code treated iOS 18.7.3 and later and iOS 26.3 and later as patched, according to Report URI.
  2. Turn on Lockdown Mode if you can’t update. When Google’s Threat Intelligence Group disclosed the Coruna kit on March 3, 2026, it recommended Lockdown Mode for devices that can’t be updated. Apple describes Lockdown Mode as an optional, extreme protection that limits some features, so treat it as a stopgap until you can update or replace the device.
  3. Check every crypto address before you send. In June 2026 research on a crypto clipper campaign, McAfee Labs advised checking the first and last six characters of the recipient address against the original source, ideally on a separate device. Because this attack also swapped addresses in links and images, confirm the address with the recipient through a channel you trust.
  4. Pay with a mobile wallet or a virtual card number when you can. The skimmer read card numbers typed into a site’s own forms. Mobile wallets and virtual card numbers from your card issuer keep your real card number off the page.
  5. Turn on transaction alerts. Most card issuers and banks can text or email you about each purchase, so you can spot a fraudulent charge the day it happens.
  6. Treat breach-related messages with suspicion. Go directly to the company’s website or app instead of clicking links in an email or text about this attack.

What to Do If You’ve Already Been Targeted

If you entered a card on an affected site:

  • Review your statements for charges after Nov. 15 and report any you don’t recognize to your card issuer.
  • Ask your issuer for a replacement card if you typed your card number into a site’s own checkout form on Nov. 16.
  • When only your card number is stolen, you aren’t responsible for unauthorized credit card charges, according to the FTC. For debit cards, the same applies if you report within 60 days of when your statement is sent.

If you sent cryptocurrency to the wrong address:

  • Contact the exchange or wallet service you used right away. Crypto transfers generally can’t be reversed, but exchanges that receive stolen funds can sometimes freeze them.
  • Save the transaction ID, both wallet addresses, the amount, and the time.

How to Report Card Fraud, Crypto Theft, and Phishing

  • Card fraud: Call your card issuer using the number on the back of your card.
  • Crypto theft or other losses: File a report with the FBI’s Internet Crime Complaint Center at ic3.gov.
  • Fraud and phishing: Report to the FTC at ReportFraud.ftc.gov.
  • Fake breach notices: Forward phishing texts to 7726 (SPAM) and report phishing emails to the company being impersonated.

Optimizely has removed the malicious code, but there are still steps you can take to protect your data and accounts. Update your iPhone, confirm crypto addresses with the recipient before sending, and check your card charges from Nov. 15 onward.

FAQ

Can Visiting a Website Hack My iPhone?

Yes, if your iPhone runs an older, vulnerable version of iOS. Exploit kits like Coruna and DarkSword can attack a device through a web page visit alone. Keeping iOS updated is the main defense.

How Can I Tell If My Card Was Skimmed Online?

You usually can’t tell at checkout, because online skimmers run invisibly on the page. Watch for unfamiliar charges, turn on transaction alerts, and report anything suspicious to your issuer. Online skimming is different from ATM skimming, which relies on a physical device attached to a card reader.

Can I Check a Website for Malware Before I Visit?

Not reliably. In this attack, the malicious code ran on trusted sites through a legitimate vendor’s script. Keeping your devices updated and checking payment details before you send them offer more protection than checking a site’s reputation.

How Do Supply Chain Attacks Affect Regular People?

When a vendor used by many websites is compromised, anyone visiting those websites can be exposed, even on sites they trust. That’s why the protective steps focus on your own device, payments, and accounts.

The post Optimizely Supply Chain Attack Hit Zoom, CNN, BBC: How to Protect Your Accounts appeared first on McAfee Blog.

❌