CVE-2025-66024
9
/ Nghiêm trọng
0.64%V4
2026-03-04
22h16 +00:00
22h16 +00:00
Thông báo cho một CVE
Luôn được thông báo về mọi thay đổi đối với một CVE cụ thể.
Mô tả CVE
The XWiki blog application allows users of the XWiki platform to create and manage blog posts. Versions starting with 9.15 and prior to 9.15.7 are vulnerable to Stored Cross-Site Scripting (XSS) via the Blog Post Title. The vulnerability arises because the post title is injected directly into the HTML tag without proper escaping. An attacker with permissions to create or edit blog posts can inject malicious JavaScript into the title field. This script will execute in the browser of any user (including administrators) who views the blog post. This leads to potential session hijacking or privilege escalation. The vulnerability has been patched in the blog application version 9.15.7 by adding missing escaping. No known workarounds are available. </div>
</div>
<div class="card card-flush py-4">
<div class="card-header">
<div class="card-title">
<h2>Thông tin CVE</h2>
</div>
</div>
<div class="card-body pt-0">
<h2 class="tw-h3">Điểm yếu liên quan</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>Tên điểm yếu</th>
<th>Nguồn</th>
</tr>
</thead>
<tbody>
<tr>
<td><nobr><a href="/vi/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>Số liệu</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>Số liệu</th>
<th>Điểm</th>
<th>Mức độ nghiêm trọng</th>
<th>CVSS Vector</th>
<th>Nguồn</th>
</tr>
</thead>
<tbody>
<tr>
<td>V3.1</td>
<td>9</td>
<td>CRITICAL</td>
<td>
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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-179407891178774" 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">Thêm thông tin</span>
</div>
<div id="metric-179407891178774" 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'>Low</p></div><div style='flex: 1;margin-left:5px;'><p>The attacker requires privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.</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'>Required</p></div><div style='flex: 1;margin-left:5px;'><p>Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited. For example, a successful exploit may only be possible during the installation of an application by a system administrator.</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'>Changed</p></div><div style='flex: 1;margin-left:5px;'><p>An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.</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>nvd@nist.gov</td>
</tr>
</tbody>
</table>
</div>
<div class="separator my-10"></div>
<h2>EPSS</h2>
<div class="mb-4">EPSS là mô hình tính điểm dự đoán khả năng một lỗ hổng bị khai thác.</div>
<h3>Điểm EPSS</h3>
<div>Mô hình EPSS tạo ra điểm xác suất từ 0 đến 1 (0 đến 100%). Điểm càng cao, xác suất một lỗ hổng bị khai thác càng lớn.</div>
<div id="chartEpss"></div>
<div style="text-align:center;">
<input type="button" class="" value="Xem bảng giá trị" onclick="$(document).ready(function() {$('#chartEpssBoard').slideToggle();});">
</div>
<div id="chartEpssBoard" style="display: none;align-content: center;">
<br><table border="1" cellspacing="0" cellpadding="5" class="table table-bordered"><thead><tr><th>Ngày</th><th>EPSS V0</th><th>EPSS V1</th><th>EPSS V2<br>(> 2022-02-04)</th><th>EPSS V3<br>(> 2025-03-07)</th><th>EPSS V4<br>(> 2025-03-17)</th></tr></thead><tbody><tr><td>2026-03-05</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.04%</td></tr><tr><td>2026-03-15</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.04%</td></tr><tr><td>2026-04-05</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.05%</td></tr><tr><td>2026-04-26</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.57%</td></tr><tr><td>2026-05-10</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.86%</td></tr><tr><td>2026-05-17</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.99%</td></tr><tr><td>2026-05-31</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.64%</td></tr></tbody></table> </div>
<h3>Phân vị EPSS</h3>
<div>Phân vị được dùng để xếp hạng CVE theo điểm EPSS. Ví dụ, một CVE ở phân vị thứ 95 theo điểm EPSS có nhiều khả năng bị khai thác hơn 95% CVE khác. Do đó, phân vị được dùng để so sánh điểm EPSS của một CVE với các CVE khác.</div>
<div id="chartPercentile"></div>
<div class="text-center">
<a href="https://www.first.org/epss/" target="_parent">EPSS First.org<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>
</div>
<div style="text-align:center;">
<input type="button" class="" value="Xem bảng giá trị" onclick="$(document).ready(function() {$('#chartPercentileBoard').slideToggle();});">
</div>
<div id="chartPercentileBoard" style="display: none;align-content: center;">
<br><table border="1" cellspacing="0" cellpadding="5" class="table table-bordered"><thead><tr><th>Ngày</th><th>Phân vị</th></tr></thead><tbody><tr><td>2026-03-05</td><td>1%</td></tr><tr><td>2026-03-15</td><td>12%</td></tr><tr><td>2026-04-05</td><td>14%</td></tr><tr><td>2026-04-26</td><td>69%</td></tr><tr><td>2026-05-10</td><td>75%</td></tr><tr><td>2026-05-17</td><td>77%</td></tr><tr><td>2026-05-31</td><td>71%</td></tr></tbody></table> </div>
<script>
var optionsEpss = {
chart: {
fontFamily: 'inherit',
type: 'area',
height: 250
},
series: [
{name: 'EPSS V0',data: [null,null,null,null,null,null,null]},
{name: 'EPSS V1',data: [null,null,null,null,null,null,null]},
{name: 'EPSS V2',data: [null,null,null,null,null,null,null]},
{name: 'EPSS V3',data: [null,null,null,null,null,null,null]},
{name: 'EPSS V4',data: [0.04,0.04,0.05,0.57,0.86,0.99,0.64]}
],
xaxis: {
categories: [1772673649000,1773537649000,1775348450000,1777162849000,1778372450000,1778977249000,1780186855000],
type: 'datetime'
},
stroke: {
curve: 'straight',
},
tooltip: {
x: {
format: 'yyyy-dd-MM'
},
y: {
formatter: function(value) {
if (value!=null)
return `${value}%`;
}
}
},
dataLabels: {
enabled: true,
formatter: function (val) {
if (val!=null)
return val + '%';
}
}
};
</script>
<script>
var optionsPercentile = {
chart: {
fontFamily: 'inherit',
type: 'area',
height: 250
},
series: [{
name: 'Percentile',
data: [10,12,14,69,75,77,71]
}],
xaxis: {
categories: [1772673649000,1773537649000,1775348450000,1777162849000,1778372450000,1778977249000,1780186855000],
type: 'datetime'
},
stroke: {
curve: 'straight',
},
tooltip: {
x: {
format: 'yyyy-dd-MM'
},
y: {
formatter: function(value) {
if (value!=null)
return `${value}%`;
}
}
},
dataLabels: {
enabled: true,
formatter: function (val) {
if (val!=null)
return val + '%';
}
}
};
</script>
<div class="separator my-10"></div>
<h2 class="tw-h3">Sản phẩm được đề cập</h2>
<h3 class='tw-h4'>Cấu hình 0</h3><p>Xwiki>>Blog_application >> Version Đến (không bao gồm) 9.15.7</p> <div class="separator my-10"></div>
<h2 class='tw-h3'>Tài liệu tham khảo</h2><div style='margin-bottom: 10px;'><a href='https://github.com/xwiki-contrib/application-blog/commit/cca87f0a0edc2e7e049d46d51f4a4d8f78b714ba' target='_blank'>https://github.com/xwiki-contrib/application-blog/commit/cca87f0a0edc2e7e049d46d51f4a4d8f78b714ba <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 : Patch</span></div><div style='margin-bottom: 10px;'><a href='https://github.com/xwiki-contrib/application-blog/commit/cdcbf2816e9b329e8f006be4391a7ffe80d4bb3f' target='_blank'>https://github.com/xwiki-contrib/application-blog/commit/cdcbf2816e9b329e8f006be4391a7ffe80d4bb3f <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></div><div style='margin-bottom: 10px;'><a href='https://github.com/xwiki-contrib/application-blog/security/advisories/GHSA-h2xq-h7f9-vh6c' target='_blank'>https://github.com/xwiki-contrib/application-blog/security/advisories/GHSA-h2xq-h7f9-vh6c <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://jira.xwiki.org/browse/BLOG-245' target='_blank'>https://jira.xwiki.org/browse/BLOG-245 <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 : Exploit, Vendor 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="/vi/official.html" class="menu-link px-2">Đối tác cơ sở dữ liệu</a>
</li>
<li class="menu-item">
<a href="/vi/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">Quản lý cookie</a>
</li>
<li class="menu-item">
<a href="/vi/contact.html" class="menu-link px-2">Liên hệ</a>
</li>
<li class="menu-item">
<a href="/vi/plan-price.html" class="menu-link px-2">Mua hàng</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">
Thông tin trình bày trên CVE Find đến từ nhiều nguồn tham chiếu được chọn lọc cẩn thận. Dữ liệu CVE được cung cấp bởi <a href="https://cve.mitre.org/" target="_blank">MITRE Corporation</a> và <a href="https://nvd.nist.gov/" target="_blank">Cơ sở dữ liệu lỗ hổng quốc gia (NVD)</a>. Danh mục lỗ hổng đã bị khai thác đã biết (KEV) có nguồn từ <a href="https://www.cisa.gov/known-exploited-vulnerabilities-catalog" target="_blank">Cơ quan An ninh mạng và Cơ sở hạ tầng (CISA)</a>, trong khi điểm EPSS đến từ <a href="https://www.first.org/epss/" target="_blank">FIRST.org</a>. Ngoài ra, dữ liệu về điểm yếu phần mềm (CWE) và mẫu tấn công phổ biến (CAPEC) được duy trì bởi <a href="https://mitre.org/" target="_blank">MITRE Corporation</a>, và thông tin về cấu hình phần cứng và phần mềm (CPE) được cung cấp bởi <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.vi.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>