취약점 (CVE)

공통 취약점 및 노출

취약점 목록

전체 CVE
CISA - 악용된 취약점
OWASP - 취약점
카테고리별 CVE
벤더로 검색
제품으로 검색

연도별 정렬

CVE 2026
CVE 2025

CVE 통계

연도/월별 CVE
카테고리별 CVE
OWASP별 CVE
CVSS 점수별 CVE
CVE가 있는 상위 100개 벤더
CVE가 있는 상위 100개 제품

특수 뷰

CVE 긴급 점수
CVE EPSS > 70%
CVE 높은 점수
CVE 네트워크 (벡터)
CVE 로컬 (벡터)
CVE 물리적 (벡터)

CVE

CVE(공통 취약점 및 노출)는 공개적으로 공개된 컴퓨터 보안 결함 목록입니다.

OWASP

OWASP Top 10은 웹 애플리케이션의 상위 10가지 보안 취약점을 식별하고 문서화하는 이니셔티브입니다.

CISA KEV

CISA 알려진 악용 취약점(KEV)은 알려진 악용 취약점 목록을 식별하고 게시하는 이니셔티브입니다.

제조사 & 제품 (CPE)

벤더 및 제품

벤더 목록

모든 벤더
CVE가 있는 상위 100개 벤더

제품 목록

모든 제품
CVE가 있는 상위 100개 제품

CPE(공통 플랫폼 열거)는 하드웨어, 소프트웨어 및 운영 체제의 이름을 지정하는 표준화된 체계입니다.

약점 (CWE)

공통 약점 열거

CWE 목록

전체 CWE
CWE 뷰
CWE 카테고리

특수 뷰

CWE Top 25 (2023)
CWE Top 25 (2022)
CWE Top 25 (2021)
소프트웨어 개발
하드웨어 설계
연구 개념

최신 CWE 5개

CWE-1463
(2026-10-28 00:00 +00:00)
CWE-1462
(2026-10-28 00:00 +00:00)
CWE-1466
(2026-10-28 00:00 +00:00)
CWE-1465
(2026-10-28 00:00 +00:00)
CWE-1464
(2026-10-28 00:00 +00:00)

CWE(공통 약점 열거)는 소프트웨어 약점 및 취약점의 포괄적인 목록 및 분류입니다.

공격 패턴 (CAPEC)

공통 공격 패턴 열거 및 분류

CAPEC 목록

전체 CAPEC
CAPEC 뷰
CAPEC 카테고리

특수 뷰

공격 메커니즘
공격 도메인
WASC 위협 분류 2.0
ATT&CK 관련 패턴
OWASP 관련 패턴

최신 CAPEC 5개

CAPEC-701
(2023-01-24 00:00 +00:00)
CAPEC-700
(2023-01-24 00:00 +00:00)
CAPEC-702
(2023-01-24 00:00 +00:00)
CAPEC-699
(2023-01-24 00:00 +00:00)
CAPEC-691
(2022-09-29 00:00 +00:00)

CAPEC(공통 공격 패턴 열거 및 분류)은 사이버 공격에서 적대자가 사용하는 공통 공격 패턴을 문서화하는 리소스입니다.

서비스 & 가격

가격 및 라이선스
계정 만들기

도움말 & 정보

FAQ & 도움말
블로그 & 기사
데이터베이스 파트너
문의하기

검색: CVE ID, CWE ID, CAPEC ID, 벤더 또는 CVE 키워드

최근 검색:

결과 없음

다른 검색어로 다시 시도하세요

English
Français
Deutsch
Español
Italiano
Português
Nederlands
Polski
日本語
简体中文
繁體中文
한국어
Bahasa Indonesia
Tiếng Việt

라이트
다크
시스템

CVE Find - 알림 시스템

언제나 최신 정보 파악

무료 계정 만들기 무료 계정 열기
계정에 로그인 알림 관리

CVE-2025-31136 : 상세 정보

홈
공통 취약점 및 노출(CVE)
CVE-2025-31136 : 상세 정보

CVE-2025-31136

점수 / 심각도

6.7

/

보통

EPSS

0.23%V4

게시일

2025-06-04
19h42 +00:00

카테고리

Cross-site Scripting

OWASP

A03-Injection

벡터

Network

수정일

2025-06-04
20h18 +00:00

공식 링크

특정 CVE 알림

특정 CVE의 변경 사항에 대한 정보를 받아보세요.

맞춤 알림

개인 알림을 활성화하세요!

알림을 활성화하려면 무료 계정에 로그인하기만 하면 됩니다. 아직 로그인하지 않으셨다면 아래 옵션 중 하나를 선택하세요.

계정에 로그인 무료 계정 만들기

특정 CVE 알림

특정 CVE의 변경 사항에 대한 정보를 받아보세요.

알림 발송 기준: 마지막 알림과 비교하여 CISA, EPSS, CVSS, CWE, 솔루션, CPE의 차이.

매개변수

발송될 알림에서 검색할 수 있는 제목을 지정할 수 있습니다.

CVE-2025-1234 형식으로 CVE ID를 입력하세요

예약

빈도?

상위 플랜 필요

매 시간 게시에 즉각적인 반응

상위 플랜 필요

매일 선택한 요일에 이메일 발송

상위 플랜 필요

매주 선택한 날에 요약 발송

매월 월간 요약

시간

분

적용 요일

월요일 화요일 수요일 목요일 금요일 토요일 일요일

실행 시간 (UTC)

적용 요일

실행 시간 (UTC)

월

매월 선택한 월

1월 2월 3월 4월 5월 6월 7월 8월 9월 10월 11월 12월

일

실행 시간 (UTC)

* 필수 항목

생성일

-

마지막 실행

-

다음 실행

-

CVE 설명

FreshRSS vulnerable to Cross-site Scripting by 'ing a vulnerable same-origin page in a feed entry</h3> FreshRSS is a self-hosted RSS feed aggregator. Prior to version 1.26.2, it's possible to run arbitrary JavaScript on the feeds page. This occurs by combining a cross-site scripting (XSS) issue that occurs in `f.php` when SVG favicons are downloaded from an attacker-controlled feed containing `<script>` tags inside of them that aren't sanitized, with the lack of CSP in `f.php` by embedding the malicious favicon in an iframe (that has `sandbox="allow-scripts allow-same-origin"` set as its attribute). An attacker needs to control one of the feeds that the victim is subscribed to, and also must have an account on the FreshRSS instance. Other than that, the iframe payload can be embedded as one of two options. The first payload requires user interaction (the user clicking on the malicious feed entry) with default user configuration, and the second payload fires instantly right after the user adds the feed or logs into the account while the feed entry is still visible. This is because of lazy image loading functionality, which the second payload bypasses. An attacker can gain access to the victim's account by exploiting this vulnerability. If the victim is an admin it would be possible to delete all users (cause damage) or execute arbitrary code on the server by modifying the update URL using fetch() via the XSS. Version 1.26.2 has a patch for the issue. </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="/ko/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>V3.1</td> <td>6.7</td> <td>MEDIUM</td> <td> CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:L <div class="m-0"> <div class="d-flex align-items-center collapsible toggle mb-0 collapsed" data-bs-toggle="collapse" data-bs-target="#metric-179407878268668" 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-179407878268668" 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'>High</p></div><div style='flex: 1;margin-left:5px;'><p> successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected.</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'>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'>Low</p></div><div style='flex: 1;margin-left:5px;'><p>Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.</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> <tr> <td>V3.1</td> <td>5.4</td> <td>MEDIUM</td> <td> CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A: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-179407878220162" 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-179407878220162" 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'>Low</p></div><div style='flex: 1;margin-left:5px;'><p>There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.</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'>Low</p></div><div style='flex: 1;margin-left:5px;'><p>Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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'>None</p></div><div style='flex: 1;margin-left:5px;'><p>There is no impact to availability within the impacted component.</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는 취약점이 악용될 가능성을 예측하는 점수 모델입니다.</div> <h3>EPSS 점수</h3> <div>EPSS 모델은 0과 1(0~100%) 사이의 확률 점수를 생성합니다. 점수가 높을수록 취약점이 악용될 가능성이 높습니다.</div> <div id="chartEpss"></div> <div style="text-align:center;"> <input type="button" class="" value="값 테이블 보기" 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>날짜</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>2025-06-05</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.05%</td></tr><tr><td>2025-06-11</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.04%</td></tr><tr><td>2025-06-16</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.04%</td></tr><tr><td>2025-06-18</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.04%</td></tr><tr><td>2025-06-19</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.04%</td></tr><tr><td>2025-06-20</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.04%</td></tr><tr><td>2025-06-23</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.04%</td></tr><tr><td>2025-07-06</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.05%</td></tr><tr><td>2025-08-11</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.05%</td></tr><tr><td>2025-09-08</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.05%</td></tr><tr><td>2025-10-04</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.07%</td></tr><tr><td>2025-10-31</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.03%</td></tr><tr><td>2025-11-01</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.03%</td></tr><tr><td>2025-11-12</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.04%</td></tr><tr><td>2025-11-18</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.08%</td></tr><tr><td>2025-11-21</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.04%</td></tr><tr><td>2025-12-29</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.04%</td></tr><tr><td>2026-01-05</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.04%</td></tr><tr><td>2026-01-07</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.04%</td></tr><tr><td>2026-01-08</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.05%</td></tr><tr><td>2026-02-22</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.09%</td></tr><tr><td>2026-03-01</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.1%</td></tr><tr><td>2026-03-22</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.11%</td></tr><tr><td>2026-04-05</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.3%</td></tr><tr><td>2026-05-17</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.3%</td></tr><tr><td>2026-06-14</td><td>–</td><td>–</td><td>–</td><td>–</td><td>0.23%</td></tr></tbody></table> </div> <h3>EPSS 백분위수</h3> <div>백분위수는 EPSS 점수에 따라 CVE의 순위를 매기는 데 사용됩니다. 예를 들어 EPSS 점수 기준 95번째 백분위수의 CVE는 다른 CVE의 95%보다 악용될 가능성이 높습니다.</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="값 테이블 보기" 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>날짜</th><th>백분위수</th></tr></thead><tbody><tr><td>2025-06-05</td><td>14%</td></tr><tr><td>2025-06-11</td><td>12%</td></tr><tr><td>2025-06-16</td><td>11%</td></tr><tr><td>2025-06-18</td><td>12%</td></tr><tr><td>2025-06-19</td><td>11%</td></tr><tr><td>2025-06-20</td><td>12%</td></tr><tr><td>2025-06-23</td><td>11%</td></tr><tr><td>2025-07-06</td><td>14%</td></tr><tr><td>2025-08-11</td><td>16%</td></tr><tr><td>2025-09-08</td><td>17%</td></tr><tr><td>2025-10-04</td><td>22%</td></tr><tr><td>2025-10-31</td><td>8%</td></tr><tr><td>2025-11-01</td><td>7%</td></tr><tr><td>2025-11-12</td><td>1%</td></tr><tr><td>2025-11-18</td><td>2%</td></tr><tr><td>2025-11-21</td><td>1%</td></tr><tr><td>2025-12-29</td><td>14%</td></tr><tr><td>2026-01-05</td><td>13%</td></tr><tr><td>2026-01-07</td><td>14%</td></tr><tr><td>2026-01-08</td><td>17%</td></tr><tr><td>2026-02-22</td><td>25%</td></tr><tr><td>2026-03-01</td><td>27%</td></tr><tr><td>2026-03-22</td><td>29%</td></tr><tr><td>2026-04-05</td><td>53%</td></tr><tr><td>2026-05-17</td><td>54%</td></tr><tr><td>2026-06-14</td><td>46%</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,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null]}, {name: 'EPSS V1',data: [null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null]}, {name: 'EPSS V2',data: [null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null]}, {name: 'EPSS V3',data: [null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null]}, {name: 'EPSS V4',data: [0.05,0.04,0.04,0.04,0.04,0.04,0.04,0.05,0.05,0.05,0.07,0.03,0.03,0.04,0.08,0.04,0.04,0.04,0.04,0.05,0.09,0.1,0.11,0.3,0.3,0.23]} ], xaxis: { categories: [1749089468000,1749607867000,1750039873000,1750212665000,1750299068000,1750385484000,1750644682000,1751767884000,1754878270000,1757297465000,1759543862000,1761880269000,1761966672000,1762917067000,1763435462000,1763694665000,1766977864000,1767582682000,1767755476000,1767841874000,1771723241000,1772328050000,1774142449000,1775348450000,1778977249000,1781396456000], 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: [14,12,11,12,11,12,11,14,16,17,22,8,7,10,20,10,14,13,14,17,25,27,29,53,54,46] }], xaxis: { categories: [1749089468000,1749607867000,1750039873000,1750212665000,1750299068000,1750385484000,1750644682000,1751767884000,1754878270000,1757297465000,1759543862000,1761880269000,1761966672000,1762917067000,1763435462000,1763694665000,1766977864000,1767582682000,1767755476000,1767841874000,1771723241000,1772328050000,1774142449000,1775348450000,1778977249000,1781396456000], 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">언급된 제품</h2> <h3 class='tw-h4'>구성 0</h3><p>Freshrss>>Freshrss >> Version 까지 (미포함) 1.26.2</p> <div class="separator my-10"></div> <h2 class='tw-h3'>참고 자료</h2><div style='margin-bottom: 10px;'><a href='https://github.com/FreshRSS/FreshRSS/security/advisories/GHSA-f6r4-jrvc-cfmr' target='_blank'>https://github.com/FreshRSS/FreshRSS/security/advisories/GHSA-f6r4-jrvc-cfmr <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 : x_refsource_CONFIRM</span></div><div style='margin-bottom: 10px;'><a href='https://github.com/FreshRSS/FreshRSS/commit/426e3054c237c2b98667ebeacbbdb5caa88e7b1f' target='_blank'>https://github.com/FreshRSS/FreshRSS/commit/426e3054c237c2b98667ebeacbbdb5caa88e7b1f <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 : x_refsource_MISC</span></div><div class="separator my-10"></div> </div> </div> </div> </div> </div> </div>   <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="/ko/official.html" class="menu-link px-2">데이터베이스 파트너</a> </li> <li class="menu-item"> <a href="/ko/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="/ko/contact.html" class="menu-link px-2">문의</a> </li> <li class="menu-item"> <a href="/ko/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>  <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.ko.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>