<?xml version="1.0"?>
<!--<!DOCTYPE nitf SYSTEM "nitf-3-4.dtd">-->
<nitf>
  <head>
    <title id="Title"></title>
    <docdata management-doc-idref="">
      <date.issue id="CreationDate" norm="" />
      <du-key id="rev-ver" generation="1" version="Default" />
      <du-key id="Parent-Version" version="" />
      <identified-content>
        <classifier id="newspro-nitf" value="r2" />
        <classifier id="Newspro-App" value="Epaper" />
        <classifier id="Content-Type" value="Story" />
        <classifier id="storyID" value="432355" />
        <classifier id="CmsConID" value="" />
        <classifier id="Desk" value="" />
        <classifier id="Source" value="" />
        <classifier id="Edition" value="" />
        <classifier id="Category" value="-1" />
        <classifier id="UserName" value="" />
        <classifier id="PublicationDate" value="26/10/2026" />
        <classifier id="PublicationName" value="DailyStar" />
        <classifier id="IsPublished" value="Y" />
        <classifier id="IsPlaced" value="Y" />
        <classifier id="IsCompleated" value="N" />
        <classifier id="IsProofed" value="N" />
        <classifier id="User" value="" />
        <classifier id="Headline-Count" value="" />
        <classifier id="Slug-Count" value="0" />
        <classifier id="Photo-Count" value="0" />
        <classifier id="Caption-Count" value="0" />
        <classifier id="Word-Count" value="0" />
        <classifier id="Character-Count" value="0" />
        <classifier id="Location" value="" />
        <classifier id="TemplateType" value="1" />
        <classifier id="StoryType" value="Story" />
        <classifier id="Author" value="" />
        <classifier id="UOM" value="mm" />
        <classifier id="kicker" value="" />
        <classifier id="ByLine" value="" />
        <classifier id="DateLine" value="" />
        <classifier id="box-geometry" value="362,1007,656,1512" />
         <classifier id="numcol" value="2"/>
      <classifier id="ArticleStyle" value=""/>
      <classifier id="Layer" value="Layer 1"/>
         <classifier id="Epaper-Build" value="7.1.5.2"/>
  <classifier id="ProcessingDateTime" value="Sun Oct 25 2026 21:41:26 GMT+0600"/>
      </identified-content>

      <urgency id="home-page" ed-urg="0" />
      <urgency id="priority" ed-urg="0" />
      <doc-scope id="scope" value="0" />
    </docdata>
    <pubdata type="print" name="DailyStar" date.publication="20261026T000000+5.30" edition.name="Business" edition.area="BUS" position.section="DST26102602BUS-Bizinner" position.sequence="2" ex-ref="DST26102602BUS-Bizinner.indd" />
  </head>
  <body boxBorderWeightColor="" boxBorderWeight="">
<body.head>
      <hedline>
    	<hl1 id="Headline1" ul="0" ol="0" ulColor=""  ulWeight=""  olColor=""  olWeight="" textFrameColor="" orgstyle="HEAD new 25 MEDIUM" class="1" MainHead="true" style="Headline1">
		<lang class="3" colour="#000000" orgstyle="HEAD new 25 MEDIUM" style="Headline1"  font="Antonia H1" fontStyle="Medium" size="26">Websites still vulnerable despite cyber warnings </lang>
	</hl1>

       </hedline>
</body.head>
    <body.content id="Bodytext" CaptionAsBody="0">
     <block>
	<media id="1" media-type="image">
			</media>
</block>

     <p style=".Bodylaser" ul="0" ol="0"  orgstyle="FROM PAGE 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="FROM PAGE 2025" font="Antonia H1" fontStyle="Bold" size="7">FROM PAGE B1
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">It advised them to check which PHP versions are running on public-facing applications, servers, containers and hosting environments.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">The agency recommended upgrading vulnerable versions to secure releases, applying verified patches and replacing unsupported versions with ones that are still maintained.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">Organisations unable to install patches immediately should restrict public access through virtual private networks, allow connections only from approved IP addresses or remove unnecessary internet exposure, the alert said.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">CIRT also advised organisations to check server logs for suspicious requests, unexpected processes, unauthorised file changes and unusual outgoing connections. Those using managed or shared hosting should work with their providers to ensure PHP is updated.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">Temporary access restrictions can reduce the risk of attacks but cannot replace security updates, the agency warned.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">It stressed that organisations remain responsible for securing their applications and infrastructure even when third-party providers host or manage them. Those that have already applied fixes should also verify that their live systems are running the updated versions.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">“Organisations should not delay remediation until a security incident occurs,” the alert said, urging those that had received earlier notifications to act without further delay.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Bold" size="9">DIGITAL SERVICES DISRUPTED
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">The vulnerability has already disrupted digital services in Bangladesh.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">Bangladesh Bank restored its website at 8am yesterday after keeping it offline for two and a half days.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">On Saturday morning, the websites of six banks were offline. The websites of IFIC Bank, Standard Islami Bank and SBAC Bank were back online by Saturday evening. Those of Agrani Bank, Janata Bank and Bengal Commercial Bank remained offline until Sunday, when they were restored.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">The land ministry also suspended digital services on land.gov.bd for about 36 hours from midnight on October 22, following CIRT’s advisory.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">The PHP2Shell vulnerabilities could allow attackers to run malicious code on affected servers without authentication. Researchers have also warned that attackers may be able to access data stored in a website’s memory, including passwords, authentication tokens and application programming interface (API) keys.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">As the vulnerabilities affect PHP itself rather than individual website code, applications could remain at risk even if their developers have followed good coding practices.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">PHP released emergency security fixes on October 21. However, a related vulnerability disclosed on October 23 also affects the patched versions and is expected to require another update in a subsequent regular release, according to the earlier report.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">Security researchers at Wiz estimate that around 70 percent of websites worldwide could be affected.
</lang>
</p>
<p style=".Bodylaser" ul="0" ol="0"  orgstyle="BODY 2025">
	<lang class="3" style=".Bodylaser" colour="#000000" orgstyle="BODY 2025" font="Antonia H1" fontStyle="Medium" size="9">Governments in the United Kingdom, the Netherlands, France, Denmark and Finland have also taken some online services offline as a precaution.
</lang>
</p>

    </body.content>
  </body>
</nitf>