<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CVSS on PlumePHP</title><link>https://plumephp.com/tags/cvss/</link><description>Recent content in CVSS on PlumePHP</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Sun, 27 Sep 2026 15:00:00 +0800</lastBuildDate><atom:link href="https://plumephp.com/tags/cvss/index.xml" rel="self" type="application/rss+xml"/><item><title>漏洞全生命周期管理实战</title><link>https://plumephp.com/security-vulnerability-management/</link><pubDate>Sun, 27 Sep 2026 15:00:00 +0800</pubDate><guid>https://plumephp.com/security-vulnerability-management/</guid><description>&lt;h2 id="导语漏洞多到修不完才是常态"&gt;导语：漏洞多到修不完才是常态&lt;/h2&gt;
&lt;p&gt;如果扫描器报出几千个漏洞、团队要求&amp;quot;全部尽快修复&amp;quot;，结果往往是被拖垮，真正高危的反而被淹没。&lt;strong&gt;漏洞管理的核心不是把漏洞清零（这不现实），而是在有限资源里优先修复最危险、最可能被利用的漏洞，并持续度量效果。&lt;/strong&gt;&lt;/p&gt;</description></item></channel></rss>