justhtml before 1.12.0 Sanitizer Bypass via Markdown
justhtml versions <= 1.11.0 (fixed in 1.12.0) do not sufficiently escape HTML-significant characters (angle brackets) in text nodes when converting a parsed document to Markdown via to_markdown(). While a small set of Markdown metacharacters are escaped, characters such as < and > are preserved, so untrusted input that is safe in to_html() — including entity-decoded text (e.g. <script>) or text from RCDATA/RAWTEXT-parsed elements like , <textarea>, <noscript>, and <plaintext> — can be emitted as raw HTML in the Markdown output, enabling a sanitizer bypass and potential cross-site scripting when that output is rendered. </div>
</div>
<div class="card card-flush py-4">
<div class="card-header">
<div class="card-title">
<h2>CVE の情報</h2>
</div>
</div>
<div class="card-body pt-0">
<h2 class="tw-h3">関連する弱点</h2>
<div class="table-responsive">
<table class="table table-striped gy-7 gs-7">
<thead>
<tr class="fw-semibold fs-6 text-gray-800 border-bottom border-gray-200">
<th><nobr>CWE-ID</nobr></th>
<th>弱点名</th>
<th>出典</th>
</tr>
</thead>
<tbody>
<tr>
<td><nobr><a href="/ja/cwe/cwe-79.html">CWE-79</a></nobr></td>
<td><b>Improper Neutralization of Input During Web Page Generation</b><br>The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.</td>
<td></td>
</tr>
</tbody>
</table>
</div>
<div class="separator my-10"></div>
<h3>メトリクス</h3>
<div class="table-responsive">
<table class="table table-striped gy-7 gs-7">
<thead>
<tr class="fw-semibold fs-6 text-gray-800 border-bottom border-gray-200">
<th>メトリクス</th>
<th>スコア</th>
<th>深刻度</th>
<th>CVSS ベクター</th>
<th>出典</th>
</tr>
</thead>
<tbody>
<tr>
<td>V4.0</td>
<td>9.3</td>
<td>CRITICAL</td>
<td>
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N <div class="m-0">
<div class="d-flex align-items-center collapsible toggle mb-0 collapsed" data-bs-toggle="collapse" data-bs-target="#metric-179400177156734" aria-expanded="false">
<div class="btn btn-sm btn-icon mw-20px btn-active-color-primary me-5">
<i class="ki-duotone ki-minus-square toggle-on text-primary fs-4">
<span class="path1"></span>
<span class="path2"></span>
</i>
<i class="ki-duotone ki-plus-square toggle-off fs-4">
<span class="path1"></span>
<span class="path2"></span>
<span class="path3"></span>
</i>
</div>
<span class="text-gray-700 cursor-pointer mb-0">詳細情報</span>
</div>
<div id="metric-179400177156734" class="fs-7 ms-1 collapse" style="">
<div class="mb-4">
<div class="d-flex align-items-center ps-10 mb-n1">
<div class="text-gray-600 fs-7">
<h4 class='bg-light border border-gray-300 rounded p-2'>Base: Exploitabilty Metrics</h4><p>The Exploitability metrics reflect the characteristics of the “thing that is vulnerable”, which we refer to formally as the vulnerable system.</p><div class='tw-h5' style='padding-left:10px'>Attack Vector</div><p style='padding-left:10px'>This metric reflects the context by which vulnerability exploitation is possible.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>Network</p></div><div style='flex: 1;margin-left:5px;'><p>The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).</p></div></div><div class='tw-h5' style='padding-left:10px'>Attack Complexity</div><p style='padding-left:10px'>This metric captures measurable actions that must be taken by the attacker to actively evade or circumvent existing built-in security-enhancing conditions in order to obtain a working exploit.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>Low</p></div><div style='flex: 1;margin-left:5px;'><p>The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.</p></div></div><div class='tw-h5' style='padding-left:10px'>Attack Requirements</div><p style='padding-left:10px'>This metric captures the prerequisite deployment and execution conditions or variables of the vulnerable system that enable the attack.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>None</p></div><div style='flex: 1;margin-left:5px;'><p>The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.</p></div></div><div class='tw-h5' style='padding-left:10px'>Privileges Required</div><p style='padding-left:10px'>This metric describes the level of privileges an attacker must possess prior to successfully exploiting the vulnerability.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>None</p></div><div style='flex: 1;margin-left:5px;'><p>The attacker is unauthenticated prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.</p></div></div><div class='tw-h5' style='padding-left:10px'>User Interaction</div><p style='padding-left:10px'>This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable system.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>None</p></div><div style='flex: 1;margin-left:5px;'><p>The vulnerable system can be exploited without interaction from any human user, other than the attacker. Examples include: a remote attacker is able to send packets to a target system a locally authenticated attacker executes code to elevate privileges</p></div></div><h4 class='bg-light border border-gray-300 rounded p-2'>Base: Impact Metrics</h4><p>The Impact metrics capture the effects of a successfully exploited vulnerability. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve.</p><div class='tw-h5' style='padding-left:10px'>Confidentiality Impact</div><p style='padding-left:10px'>This metric measures the impact to the confidentiality of the information managed by the system due to a successfully exploited vulnerability.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>High</p></div><div style='flex: 1;margin-left:5px;'><p>There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.</p></div></div><div class='tw-h5' style='padding-left:10px'>Integrity Impact</div><p style='padding-left:10px'>This metric measures the impact to integrity of a successfully exploited vulnerability.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>High</p></div><div style='flex: 1;margin-left:5px;'><p>There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the Vulnerable System. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the Vulnerable System.</p></div></div><div class='tw-h5' style='padding-left:10px'>Availability Impact</div><p style='padding-left:10px'>This metric measures the impact to the availability of the impacted system resulting from a successfully exploited vulnerability.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>High</p></div><div style='flex: 1;margin-left:5px;'><p>There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the Vulnerable System; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the Vulnerable System (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).</p></div></div><div class='tw-h5' style='padding-left:10px'>Sub Confidentiality Impact</div><p style='padding-left:10px'></p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>Negligible</p></div><div style='flex: 1;margin-left:5px;'><p>There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.</p></div></div><div class='tw-h5' style='padding-left:10px'>Sub Integrity Impact</div><p style='padding-left:10px'></p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>None</p></div><div style='flex: 1;margin-left:5px;'><p>There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.</p></div></div><div class='tw-h5' style='padding-left:10px'>Sub Availability Impact</div><p style='padding-left:10px'></p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>None</p></div><div style='flex: 1;margin-left:5px;'><p>There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.</p></div></div><h4 class='bg-light border border-gray-300 rounded p-2'>Threat Metrics</h4><p>The Threat metrics measure the current state of exploit techniques or code availability for a vulnerability.</p><h4 class='bg-light border border-gray-300 rounded p-2'>Environmental Metrics</h4><p>These metrics enable the consumer analyst to customize the resulting score depending on the importance of the affected IT asset to a user’s organization, measured in terms of complementary/alternative security controls in place, Confidentiality, Integrity, and Availability. The metrics are the modified equivalent of Base metrics and are assigned values based on the system placement within organizational infrastructure.</p><h4 class='bg-light border border-gray-300 rounded p-2'>Supplemental Metrics</h4><p>Supplemental metric group provides new metrics that describe and measure additional extrinsic attributes of a vulnerability. While the assessment of Supplemental metrics is provisioned by the provider, the usage and response plan of each metric within the Supplemental metric group is determined by the consumer.</p> </div>
</div>
</div>
</div>
</div>
</td>
<td></td>
</tr>
<tr>
<td>V3.1</td>
<td>9.8</td>
<td>CRITICAL</td>
<td>
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H <div class="m-0">
<div class="d-flex align-items-center collapsible toggle mb-0 collapsed" data-bs-toggle="collapse" data-bs-target="#metric-179400177142813" aria-expanded="false">
<div class="btn btn-sm btn-icon mw-20px btn-active-color-primary me-5">
<i class="ki-duotone ki-minus-square toggle-on text-primary fs-4">
<span class="path1"></span>
<span class="path2"></span>
</i>
<i class="ki-duotone ki-plus-square toggle-off fs-4">
<span class="path1"></span>
<span class="path2"></span>
<span class="path3"></span>
</i>
</div>
<span class="text-gray-700 cursor-pointer mb-0">詳細情報</span>
</div>
<div id="metric-179400177142813" class="fs-7 ms-1 collapse" style="">
<div class="mb-4">
<div class="d-flex align-items-center ps-10 mb-n1">
<div class="text-gray-600 fs-7">
<h4 class='bg-light border border-gray-300 rounded p-2'>Base: Exploitabilty Metrics</h4><p>The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.</p><div class='tw-h5' style='padding-left:10px'>Attack Vector</div><p style='padding-left:10px'>This metric reflects the context by which vulnerability exploitation is possible.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>Network</p></div><div style='flex: 1;margin-left:5px;'><p>The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).</p></div></div><div class='tw-h5' style='padding-left:10px'>Attack Complexity</div><p style='padding-left:10px'>This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>Low</p></div><div style='flex: 1;margin-left:5px;'><p>Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.</p></div></div><div class='tw-h5' style='padding-left:10px'>Privileges Required</div><p style='padding-left:10px'>This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>None</p></div><div style='flex: 1;margin-left:5px;'><p>The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.</p></div></div><div class='tw-h5' style='padding-left:10px'>User Interaction</div><p style='padding-left:10px'>This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>None</p></div><div style='flex: 1;margin-left:5px;'><p>The vulnerable system can be exploited without interaction from any user.</p></div></div><h4 class='bg-light border border-gray-300 rounded p-2'>Base: Scope Metrics</h4><p>The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope.</p><div class='tw-h5' style='padding-left:10px'>Scope</div><p style='padding-left:10px'>Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>Unchanged</p></div><div style='flex: 1;margin-left:5px;'><p>An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.</p></div></div><h4 class='bg-light border border-gray-300 rounded p-2'>Base: Impact Metrics</h4><p>The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve.</p><div class='tw-h5' style='padding-left:10px'>Confidentiality Impact</div><p style='padding-left:10px'>This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>High</p></div><div style='flex: 1;margin-left:5px;'><p>There is a total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.</p></div></div><div class='tw-h5' style='padding-left:10px'>Integrity Impact</div><p style='padding-left:10px'>This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>High</p></div><div style='flex: 1;margin-left:5px;'><p>There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.</p></div></div><div class='tw-h5' style='padding-left:10px'>Availability Impact</div><p style='padding-left:10px'>This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.</p><div style='display:flex;padding-left:10px;'><div style='width:70px;'><p class='text-center bg-gray-800 text-gray-100 rounded'>High</p></div><div style='flex: 1;margin-left:5px;'><p>There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).</p></div></div><h4 class='bg-light border border-gray-300 rounded p-2'>Temporal Metrics</h4><p>The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability.</p><h4 class='bg-light border border-gray-300 rounded p-2'>Environmental Metrics</h4><p>These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.</p> </div>
</div>
</div>
</div>
</div>
</td>
<td></td>
</tr>
</tbody>
</table>
</div>
<div class="separator my-10"></div>
<h2 class='tw-h3'>参考資料</h2><div style='margin-bottom: 10px;'><a href='https://github.com/EmilStenstrom/justhtml/security/advisories/GHSA-3rcm-vjrc-p45j' target='_blank'>https://github.com/EmilStenstrom/justhtml/security/advisories/GHSA-3rcm-vjrc-p45j <i class="ki-duotone ki-exit-right-corner" style="font-size: 10px;vertical-align:8px"><span class="path1"></span><span class="path2"></span></i></a><br><span style='margin-left:20px;'>Tags : vendor-advisory</span></div><div style='margin-bottom: 10px;'><a href='https://www.vulncheck.com/advisories/justhtml-before-sanitizer-bypass-via-markdown' target='_blank'>https://www.vulncheck.com/advisories/justhtml-before-sanitizer-bypass-via-markdown <i class="ki-duotone ki-exit-right-corner" style="font-size: 10px;vertical-align:8px"><span class="path1"></span><span class="path2"></span></i></a><br><span style='margin-left:20px;'>Tags : third-party-advisory</span></div><div class="separator my-10"></div> </div>
</div>
</div>
</div>
</div>
</div>
<!--end::Container-->
<!--begin::Footer-->
<div class="footer py-4 d-flex flex-lg-column" id="kt_footer">
<div class="container-xxl d-flex flex-column flex-md-row align-items-center justify-content-between">
<div class="text-gray-900 order-2 order-md-1">
<span class="text-muted fw-semibold me-1">2026©</span>
<a href="https://www.tesweb.com" target="_blank" class="text-gray-800 text-hover-primary">tesweb SA</a>,
<a href="https://www.bexxo.ch" target="_blank" class="text-gray-800 text-hover-primary">bexxo Cyber Security</a>
</div>
<ul class="menu menu-gray-600 menu-hover-primary fw-semibold order-1">
<li class="menu-item">
<a href="/ja/official.html" class="menu-link px-2">データ提供元</a>
</li>
<li class="menu-item">
<a href="/ja/gdpr.html" class="menu-link px-2">GDPR</a>
</li>
<li class="menu-item">
<a href="#" id="gdpr-manage-cookies" class="menu-link px-2">クッキーを管理する</a>
</li>
<li class="menu-item">
<a href="/ja/contact.html" class="menu-link px-2">お問い合わせ</a>
</li>
<li class="menu-item">
<a href="/ja/plan-price.html" class="menu-link px-2">購入</a>
</li>
<li class="menu-item">
<a href="https://www.linkedin.com/company/cve-find/" class="menu-link px-2" target="_blank"><img src="/media/social/linkedin.svg" width="40" height="40" alt="LinkedIn Account"/></a>
</li>
<li class="menu-item">
<a href="https://www.facebook.com/people/CVE-Find-Alert/61561116452093/" class="menu-link px-2" target="_blank"><img src="/media/social/facebook.svg" width="40" height="40" alt="Facebook Account"/></a>
</li>
<li class="menu-item">
<a href="https://x.com/cvefindcom" class="menu-link px-2" target="_blank"><img src="/media/social/twitter.svg" width="40" height="40" alt="Twitter Account"/></a>
</li>
</ul>
</div>
</div>
<div class="footer py-4">
<div class="container-xxl align-items-center justify-content-between">
CVE Findに掲載されている情報は、慎重に選定された複数の参照ソースから取得されています。CVEデータは<a href="https://cve.mitre.org/" target="_blank">MITRE Corporation</a>および<a href="https://nvd.nist.gov/" target="_blank">国家脆弱性データベース（NVD）</a>が提供しています。既知の悪用された脆弱性（KEV）カタログは<a href="https://www.cisa.gov/known-exploited-vulnerabilities-catalog" target="_blank">サイバーセキュリティ・インフラセキュリティ庁（CISA）</a>から、EPSSスコアは<a href="https://www.first.org/epss/" target="_blank">FIRST.org</a>から取得しています。また、ソフトウェアの弱点（CWE）および共通攻撃パターン（CAPEC）に関するデータは<a href="https://mitre.org/" target="_blank">MITRE Corporation</a>が管理し、ハードウェアおよびソフトウェア構成（CPE）に関する情報は<a href="https://nvd.nist.gov/products/cpe" target="_blank">NVD</a>が提供しています。 </div>
</div>
</div>
</div>
</div>
<!--begin::Javascript-->
<script>var hostUrl = "assets/";</script>
<script src="/plugins/global/plugins.bundle.min.1743008562.js"></script>
<script src="/js/scripts.bundle.1718974735.js"></script>
<script src="/js/app/custom.min.1788264851.js"></script>
<script src="/js/app/base.ja.min.1793721674.js" defer></script>
<script src="/plugins/custom/datatables/datatables.bundle.1718974031.js"></script>
<script src="/js/aceeditor/ace.1715679271.js"></script>
<script src="/js/app/bloc/cve/epss.min.1738322185.js"></script>
<script src="/js/app/bloc/cve/exploitdb.min.1738322201.js"></script>
<script src="/js/app/account/manageAlertNeedAccount.min.1782998772.js" defer></script>
<div class="ea-slot d-lg-none" data-ea-anchor="mobile" data-ea-pub="cvefindcom" data-ea-type="text" data-ea-style="fixedfooter" data-ea-kw="security|cybersecurity|vulnerability|cve"></div> <style>
/* Encart EthicalAds centré dans son emplacement */
.ea-slot [data-ea-publisher]{margin-left:auto;margin-right:auto;}
/* Format horizontal : remplit la largeur de la colonne (variable officielle EthicalAds) */
.ea-slot [data-ea-publisher].horizontal{--ea-image-placement-width-horizontal:100%;}
</style>
<script async src="https://media.ethicalads.io/media/client/ethicalads.min.js"></script>
<script src="/js/app/ads/ethicalads.min.1792667231.js" defer></script>
</body>
</html>
<script>
var cookieTimezoneBrowser = function () {
let timeZone = Intl.DateTimeFormat().resolvedOptions().timeZone;
var offset = -new Date().getTimezoneOffset();
var prefix = offset >= 0 ? '+' : '-';
var timezoneOffset = prefix + Math.floor(Math.abs(offset) / 60).toString().padStart(2, '0') + ':' + (Math.abs(offset) % 60).toString().padStart(2, '0');
document.cookie = "tw-browser=" + timeZone+"|"+ timezoneOffset+ "; path=/";
}
cookieTimezoneBrowser();
</script> 