<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: zast ai</title>
    <description>The latest articles on Forem by zast ai (@zast_ai_0day).</description>
    <link>https://forem.com/zast_ai_0day</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3444041%2Ffbca4f67-8f04-452e-acc5-60d655b08aa0.jpeg</url>
      <title>Forem: zast ai</title>
      <link>https://forem.com/zast_ai_0day</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/zast_ai_0day"/>
    <language>en</language>
    <item>
      <title>ZAST.AI Security Advisory: Critical SSRF Resolved in ClawdBot.</title>
      <dc:creator>zast ai</dc:creator>
      <pubDate>Tue, 27 Jan 2026 15:17:06 +0000</pubDate>
      <link>https://forem.com/zast_ai_0day/zast-security-advisory-critical-ssrf-resolved-in-clawdbot-4hno</link>
      <guid>https://forem.com/zast_ai_0day/zast-security-advisory-critical-ssrf-resolved-in-clawdbot-4hno</guid>
      <description>&lt;p&gt;While the community focused on general configuration risks, ZAST verified the actual code.&lt;/p&gt;

&lt;p&gt;Our engine autonomously identified a high-severity SSRF vulnerability exploitable via DNS Rebinding. The flaw was a classic TOCTOU (Time-of-Check to Time-of-Use) gap, allowing attackers to bypass validation and access internal networks.&lt;/p&gt;

&lt;p&gt;The Resolution: Our Co-founder Chris Zheng reported this to the maintainer (@steipete), who acknowledged the issue and pushed a fix immediately.&lt;/p&gt;

&lt;p&gt;The project has now implemented DNS Pinning to eliminate the vector. We are proud to be credited in the changelog for securing the ecosystem.&lt;/p&gt;

&lt;p&gt;View the official fix: &lt;a href="https://github.com/clawdbot/clawdbot/commit/b623557a2ec7e271bda003eb3ac33fbb2e218505" rel="noopener noreferrer"&gt;https://github.com/clawdbot/clawdbot/commit/b623557a2ec7e271bda003eb3ac33fbb2e218505&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fz5v1qanhxvdkv9so365e.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fz5v1qanhxvdkv9so365e.png" alt=" " width="800" height="440"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>appsec</category>
      <category>cybersecurity</category>
      <category>ssrf</category>
      <category>clawdbot</category>
    </item>
    <item>
      <title>A Stored XSS (CVE-2026-0693) in the "Allow HTML in Category Descriptions" @WordPress plugin.</title>
      <dc:creator>zast ai</dc:creator>
      <pubDate>Sat, 24 Jan 2026 02:20:17 +0000</pubDate>
      <link>https://forem.com/zast_ai_0day/a-stored-xss-in-the-html-in-category-descriptions-wordpress-plugin-2dch</link>
      <guid>https://forem.com/zast_ai_0day/a-stored-xss-in-the-html-in-category-descriptions-wordpress-plugin-2dch</guid>
      <description>&lt;p&gt;We verified a Stored XSS (CVE-2026-0693) in the "HTML in Category Descriptions" @WordPress plugin.&lt;/p&gt;

&lt;p&gt;The Flaw: The plugin correctly restricts input but unintentionally removes global output filters (wp_kses_data) for all users. The Impact: Malicious scripts in category descriptions execute for any visitor. The Validation: Confirmed via autonomous PoC.&lt;/p&gt;

&lt;p&gt;Security requires validating the full data lifecycle, not just lines of code.&lt;/p&gt;

&lt;p&gt;Vulnerability details: &lt;a href="https://www.cve.org/CVERecord?id=CVE-2026-0693" rel="noopener noreferrer"&gt;https://www.cve.org/CVERecord?id=CVE-2026-0693&lt;/a&gt;&lt;/p&gt;

</description>
      <category>wordpresssecurity</category>
      <category>appsec</category>
      <category>zast</category>
    </item>
    <item>
      <title>2025 Annual Report: 153 Publicly Disclosed Vulnerabilities &amp; 0 False Positives</title>
      <dc:creator>zast ai</dc:creator>
      <pubDate>Wed, 14 Jan 2026 14:06:06 +0000</pubDate>
      <link>https://forem.com/zast_ai_0day/2025-annual-report-153-verified-vulnerabilities-0-false-positives-4380</link>
      <guid>https://forem.com/zast_ai_0day/2025-annual-report-153-verified-vulnerabilities-0-false-positives-4380</guid>
      <description>&lt;p&gt;In 2025, ZAST.AI redefined what’s possible in static analysis. It successfully identified and verified critical logic flaws in enterprise infrastructure including Microsoft Azure SDK, Alibaba Nacos, Apache Struts2, Apache Commons, Koa, Langfuse, Node-Formidable, WordPress and more.&lt;/p&gt;

&lt;p&gt;🔍 153 Vulnerabilities Publicly Disclosed&lt;br&gt;
🔒 119 CVEs Assigned&lt;br&gt;
🎯 0 False Positives&lt;/p&gt;

&lt;p&gt;Every alert backed by an executable PoC. No noise. Just proof.&lt;/p&gt;

&lt;p&gt;🔗 &lt;a href="https://blog.zast.ai/research/vulnerability%20reports/cybersecurity/The-2025-Bug-Hunter-Report-How-ZAST.AI-Uncovered-115+-Verified-CVE" rel="noopener noreferrer"&gt;https://blog.zast.ai/research/vulnerability%20reports/cybersecurity/The-2025-Bug-Hunter-Report-How-ZAST.AI-Uncovered-115+-Verified-CVE&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fcnximsai3lm8xolkv0ed.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fcnximsai3lm8xolkv0ed.png" alt=" " width="800" height="477"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>cybersecurity</category>
      <category>devsecops</category>
      <category>appsec</category>
      <category>cve</category>
    </item>
    <item>
      <title>CRITICAL ALERT: Apache Struts2 XXE Exposed (CVE-2025-68493)</title>
      <dc:creator>zast ai</dc:creator>
      <pubDate>Tue, 13 Jan 2026 13:02:51 +0000</pubDate>
      <link>https://forem.com/zast_ai_0day/critical-alert-apache-struts2-xxe-exposed-cve-2025-68493-2heh</link>
      <guid>https://forem.com/zast_ai_0day/critical-alert-apache-struts2-xxe-exposed-cve-2025-68493-2heh</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fy625xb56871cvlrdo85h.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fy625xb56871cvlrdo85h.jpg" alt=" " width="800" height="436"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;ZAST.AI discovered a high severity XXE vulnerability in XWork-Core allows threat actors steal files &amp;amp; trigger SSRF.&lt;/p&gt;

&lt;p&gt;The flaw was hidden in DomHelper's unconfigured SAX parser.&lt;/p&gt;

&lt;p&gt;⚡ Discovered by ZAST.ai AI Agent — proving once again that AI-driven logic beats pattern matching.&lt;/p&gt;

&lt;p&gt;Patch immediately (Struts2 &amp;lt;= 6.0.3)!&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fpvf8gpddf9rtn7cidnxr.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fpvf8gpddf9rtn7cidnxr.jpg" alt=" " width="800" height="526"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;🔗 Vulnerability reports: &lt;a href="https://cwiki.apache.org/confluence/display/WW/S2-069" rel="noopener noreferrer"&gt;https://cwiki.apache.org/confluence/display/WW/S2-069&lt;/a&gt;&lt;/p&gt;

</description>
      <category>appsec</category>
      <category>cybersecurity</category>
      <category>xxe</category>
      <category>apachestruts2</category>
    </item>
    <item>
      <title>ZAST.AI vs. Burp Suite: The Signal vs. Noise Challenge 🥊</title>
      <dc:creator>zast ai</dc:creator>
      <pubDate>Tue, 23 Dec 2025 13:40:46 +0000</pubDate>
      <link>https://forem.com/zast_ai_0day/zastai-vs-burp-suite-the-signal-vs-noise-challenge-36kj</link>
      <guid>https://forem.com/zast_ai_0day/zastai-vs-burp-suite-the-signal-vs-noise-challenge-36kj</guid>
      <description>&lt;p&gt;We pitted our AI engine against the industry standard to find a critical IDOR vulnerability in an open-source Java CMS. Both tools found the bug, but the difference in efficiency was staggering:&lt;br&gt;
⚠️ Burp Suite (Traditional DAST)&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;90% False Positives: Flagged 30+ endpoints based on simple status codes.&lt;br&gt;
Buried the Signal: The real critical bug was hidden in a sea of false alarms.&lt;br&gt;
Result: Your team wastes hours manually filtering noise to find the truth.&lt;br&gt;
✅ ZAST.AI (AI-Powered Assessment)&lt;br&gt;
Zero False Positives: 100% precision.&lt;br&gt;
Instant Isolation: Autonomously filtered the noise and flagged only the verified exploit.&lt;br&gt;
Result: Immediate remediation, zero wasted time.&lt;br&gt;
It's not just about finding the vulnerability; it's about isolating it from the noise.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;See the full technical breakdown: &lt;a href="https://tinyurl.com/4kzssvuw" rel="noopener noreferrer"&gt;https://tinyurl.com/4kzssvuw&lt;/a&gt;&lt;/p&gt;

</description>
      <category>appsec</category>
      <category>cybersecurity</category>
      <category>idor</category>
      <category>zerofalsepositives</category>
    </item>
    <item>
      <title>🚨 MAJOR DISCOVERY: 7 WordPress Plugin Vulnerabilities, ZERO False Positives!</title>
      <dc:creator>zast ai</dc:creator>
      <pubDate>Tue, 09 Dec 2025 13:33:30 +0000</pubDate>
      <link>https://forem.com/zast_ai_0day/major-discovery-7-wordpress-plugin-vulnerabilities-zero-false-positives-2a1h</link>
      <guid>https://forem.com/zast_ai_0day/major-discovery-7-wordpress-plugin-vulnerabilities-zero-false-positives-2a1h</guid>
      <description>&lt;p&gt;Our AI security research agent just uncovered 7 verified stored XSS flaws in WordPress plugins — missed by traditional tools!&lt;/p&gt;

&lt;p&gt;Key Vulnerabilities Found:&lt;br&gt;
✅ Double the Donation plugin (CVE-2025-12020) - CVSS 4.9&lt;br&gt;
✅ YouTube Subscribe plugin (CVE-2025-12025) - CVSS 4.4&lt;br&gt;
✅ Featured Image plugin (CVE-2025-12019) - CVSS 4.4&lt;br&gt;
✅ 4 more similar vulnerabilities in other plugins&lt;/p&gt;

&lt;p&gt;Automated PoC verification = 100% actionable results for security teams 🛡️&lt;br&gt;
🔗 Full technical report: &lt;a href="https://tinyurl.com/ms8678jc" rel="noopener noreferrer"&gt;https://tinyurl.com/ms8678jc&lt;/a&gt;&lt;/p&gt;

</description>
      <category>cybersecurity</category>
      <category>wordpress</category>
      <category>securityagent</category>
      <category>xss</category>
    </item>
    <item>
      <title>🔥 1-Month DEV CHALLENGE: Test ZAST Express (IDE Extension) in 3 Min, Win $100 &amp; Credits!</title>
      <dc:creator>zast ai</dc:creator>
      <pubDate>Mon, 01 Dec 2025 13:44:38 +0000</pubDate>
      <link>https://forem.com/zast_ai_0day/1-month-dev-challenge-test-zast-express-ide-extension-in-3-min-win-100-credits-lgf</link>
      <guid>https://forem.com/zast_ai_0day/1-month-dev-challenge-test-zast-express-ide-extension-in-3-min-win-100-credits-lgf</guid>
      <description>&lt;p&gt;Tired of switching between your IDE and security dashboards? Dealing with false alerts and slow scans?&lt;br&gt;
ZAST Express brings instant, reliable code security assessment with PoC directly to your IDE. &lt;br&gt;
In return for your valuable firsthand feedback, we've prepared Amazon Gift Cards and tons of ZAST Credits as a thank you.&lt;/p&gt;

&lt;p&gt;🎯 How to Participate (It's Easy &amp;amp; Fast):&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Install the “ZAST Express” extension from VS Code/Cursor Marketplace (takes ~1 min).&lt;/li&gt;
&lt;li&gt;Run an assessment on your own project using the extension (est. 2 mins).
Share your feedback by commenting on our official GitHub Issue:
&lt;a href="https://tinyurl.com/my5zj4tu" rel="noopener noreferrer"&gt;https://tinyurl.com/my5zj4tu&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Tag devs who need faster security checks! 🛡️&lt;/p&gt;

</description>
      <category>securitychallenge</category>
      <category>devtools</category>
      <category>idesecurity</category>
      <category>zastai</category>
    </item>
    <item>
      <title>🎊 [New Feature] ZAST EXPRESS - Official Release</title>
      <dc:creator>zast ai</dc:creator>
      <pubDate>Mon, 24 Nov 2025 14:28:06 +0000</pubDate>
      <link>https://forem.com/zast_ai_0day/new-feature-zast-express-official-release-4f1i</link>
      <guid>https://forem.com/zast_ai_0day/new-feature-zast-express-official-release-4f1i</guid>
      <description>&lt;p&gt;Our IDE extension is now officially available:&lt;br&gt;
✨ Zero-false-positive AI engine integrated into your IDE&lt;br&gt;
⚡ Instant security feedback without leaving your coding environment&lt;br&gt;
🔒 Local processing ensures maximum privacy&lt;br&gt;
🎯 Supports VS Code and Cursor with more platforms coming soon&lt;/p&gt;

&lt;p&gt;Learn more about your security copilot in IDE: &lt;a href="https://tinyurl.com/3ykth59d" rel="noopener noreferrer"&gt;https://tinyurl.com/3ykth59d&lt;/a&gt;&lt;/p&gt;

</description>
      <category>devtools</category>
      <category>vscode</category>
      <category>cursor</category>
      <category>cybersecurity</category>
    </item>
    <item>
      <title>🚀 GitHub Codespaces + ZAST.AI: Assess Apps in Minutes!</title>
      <dc:creator>zast ai</dc:creator>
      <pubDate>Tue, 18 Nov 2025 13:35:00 +0000</pubDate>
      <link>https://forem.com/zast_ai_0day/github-codespaces-zastai-assess-apps-in-minutes-3da3</link>
      <guid>https://forem.com/zast_ai_0day/github-codespaces-zastai-assess-apps-in-minutes-3da3</guid>
      <description>&lt;p&gt;No local setup—build, package, and secure your projects in the cloud ⚡&lt;br&gt;
• Zero-false-positive assessments for JS/TS, Java &amp;amp; Python (beta) 🛡️&lt;br&gt;
• Seamless DevSecOps workflows for multiple tech stacks 🔄&lt;br&gt;
• Free 120 GitHub Codespaces hours/month 🆓&lt;/p&gt;

&lt;p&gt;Read the step-by-step guide: &lt;a href="https://tinyurl.com/yfehvmck" rel="noopener noreferrer"&gt;https://tinyurl.com/yfehvmck&lt;/a&gt;&lt;/p&gt;

</description>
      <category>appsecurity</category>
      <category>github</category>
      <category>vulnerabilityassessment</category>
      <category>zastai</category>
    </item>
    <item>
      <title>ZAST.AI identified 6+ vulnerabilities in JeeSite</title>
      <dc:creator>zast ai</dc:creator>
      <pubDate>Tue, 11 Nov 2025 14:50:46 +0000</pubDate>
      <link>https://forem.com/zast_ai_0day/zastai-identified-6-vulnerabilities-in-jeesite-5a80</link>
      <guid>https://forem.com/zast_ai_0day/zastai-identified-6-vulnerabilities-in-jeesite-5a80</guid>
      <description>&lt;p&gt;🔍ZAST.AI identified 6+ vulnerabilities in JeeSite &amp;lt;=5.12.0 b522b3f:&lt;br&gt;
• SSRF (CVE-2025-7759)&lt;br&gt;
• Multiple Open Redirection flaws (CVE-2025-7763, CVE-2025-7785, CVE-2025-7863)&lt;br&gt;
• Insecure File Upload (CVE-2025-7864)&lt;br&gt;
• XSS filter bypass (CVE-2025-7865, CVE-2025-9796)&lt;/p&gt;

&lt;p&gt;👩‍💻Complete analysis: &lt;a href="https://tinyurl.com/4tryaec2" rel="noopener noreferrer"&gt;https://tinyurl.com/4tryaec2&lt;/a&gt;&lt;/p&gt;

</description>
      <category>javaframework</category>
      <category>ssrf</category>
      <category>openredirect</category>
      <category>xss</category>
    </item>
    <item>
      <title>The Same Feature That Makes a Component Powerful Can Also Make It Dangerous.</title>
      <dc:creator>zast ai</dc:creator>
      <pubDate>Tue, 04 Nov 2025 15:14:23 +0000</pubDate>
      <link>https://forem.com/zast_ai_0day/the-same-feature-that-makes-a-component-powerful-can-also-make-it-dangerous-43mk</link>
      <guid>https://forem.com/zast_ai_0day/the-same-feature-that-makes-a-component-powerful-can-also-make-it-dangerous-43mk</guid>
      <description>&lt;p&gt;A documented feature became a weapon with #Log4Shell. The blurry line between function and flaw is the new AppSec frontline.🚧&lt;/p&gt;

&lt;p&gt;Our latest post assesses critical cases like Spring4Shell and Apache Struts to answer:&lt;br&gt;
• Who is responsible when a feature is exploited? ⁉️&lt;br&gt;
• Is "secure-by-default" a myth? 🔮&lt;br&gt;
• How can we better define and manage these risks? 🧐&lt;/p&gt;

&lt;p&gt;Learn the 3 key lessons for a more secure future: &lt;a href="https://tinyurl.com/4wwmytj4" rel="noopener noreferrer"&gt;https://tinyurl.com/4wwmytj4&lt;/a&gt;&lt;/p&gt;

</description>
      <category>cybersecurity</category>
      <category>log4j</category>
      <category>appsec</category>
      <category>zerotrust</category>
    </item>
    <item>
      <title>ZAST.AI found Insecure File Upload &amp; CSP bypass issues in CodiMD</title>
      <dc:creator>zast ai</dc:creator>
      <pubDate>Tue, 28 Oct 2025 15:30:04 +0000</pubDate>
      <link>https://forem.com/zast_ai_0day/zastai-found-insecure-file-upload-csp-bypass-issues-in-codimd-1f33</link>
      <guid>https://forem.com/zast_ai_0day/zastai-found-insecure-file-upload-csp-bypass-issues-in-codimd-1f33</guid>
      <description>&lt;p&gt;• Low version (CVE-2025-46654)&lt;br&gt;
• High version (CVE-2025-46655)&lt;br&gt;
These vulnerabilities could allow attackers to upload malicious files.&lt;br&gt;
🔗 Vulnerability details: &lt;a href="https://tinyurl.com/378h3xb7" rel="noopener noreferrer"&gt;https://tinyurl.com/378h3xb7&lt;/a&gt;&lt;/p&gt;

</description>
      <category>cve</category>
      <category>fileupload</category>
      <category>websecurity</category>
      <category>zastai</category>
    </item>
  </channel>
</rss>
