CVE 설명

The Word 2 Cash plugin for WordPress is vulnerable to Cross-Site Request Forgery leading to Stored Cross-Site Scripting in versions up to and including 0.9.2. This is due to the complete absence of nonce verification on the settings save handler in the w2c_admin() function, combined with missing input sanitization before storage and missing output escaping when rendering the stored value. The w2c-definitions POST parameter is saved raw via update_option() and later echoed without escaping inside a

element. This makes it possible for unauthenticated attackers to forge a request on behalf of a logged-in administrator, storing arbitrary JavaScript payloads that execute in the WordPress admin panel whenever the settings page is visited.                            </div>
                        </div>

<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-352.html">CWE-352</a></nobr></td>
                                    <td><b>Cross-Site Request Forgery</b><br>The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. </td>
                                    <td></td>
                                </tr>
                </tbody>
            </table>
        </div>
            <div class="separator my-10"></div>

<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.1</td>
                        <td>MEDIUM</td>
                        <td>
                            CVSS:3.1/AV:N/AC:L/PR:N/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-179409356744474" 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-179409356744474" 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'>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>security@wordfence.com</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>

<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>

};
            </script>

<h2 class='tw-h3'>참고 자료</h2><div style='margin-bottom: 10px;'><a href='https://plugins.trac.wordpress.org/browser/word-2-cash/tags/0.9.2/word2cash.php#L18' target='_blank'>https://plugins.trac.wordpress.org/browser/word-2-cash/tags/0.9.2/word2cash.php#L18 <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://plugins.trac.wordpress.org/browser/word-2-cash/tags/0.9.2/word2cash.php#L20' target='_blank'>https://plugins.trac.wordpress.org/browser/word-2-cash/tags/0.9.2/word2cash.php#L20 <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://plugins.trac.wordpress.org/browser/word-2-cash/tags/0.9.2/word2cash.php#L31' target='_blank'>https://plugins.trac.wordpress.org/browser/word-2-cash/tags/0.9.2/word2cash.php#L31 <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://plugins.trac.wordpress.org/browser/word-2-cash/trunk/word2cash.php#L18' target='_blank'>https://plugins.trac.wordpress.org/browser/word-2-cash/trunk/word2cash.php#L18 <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://plugins.trac.wordpress.org/browser/word-2-cash/trunk/word2cash.php#L20' target='_blank'>https://plugins.trac.wordpress.org/browser/word-2-cash/trunk/word2cash.php#L20 <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://plugins.trac.wordpress.org/browser/word-2-cash/trunk/word2cash.php#L31' target='_blank'>https://plugins.trac.wordpress.org/browser/word-2-cash/trunk/word2cash.php#L31 <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://www.wordfence.com/threat-intel/vulnerabilities/id/e4c7ca5c-38aa-4413-83eb-29185cca2a74?source=cve' target='_blank'>https://www.wordfence.com/threat-intel/vulnerabilities/id/e4c7ca5c-38aa-4413-83eb-29185cca2a74?source=cve <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 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>

<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>

CVE-2026-6395 : 상세 정보

CVE-2026-6395

CVE 설명