Banking AI XSS: The exploit is in the payment reference
It could still use a sanitization library like DOMPurify though to at least prevent JavaScript execution.Does `<img src=x onfoo=bar>` also work? The imaginary "onfoobar" event handler is not filtered outOkay, it's getting dangerously close..How about the classic `<img src=x onerror=alert(1)>`? An `<img>` tag with an event handler is rendered, which fires without additional user interaction2.
- ▪It could still use a sanitization library like DOMPurify though to at least prevent JavaScript execution.Does `<img src=x onfoo=bar>` also work?
- ▪The imaginary "onfoobar" event handler is not filtered outOkay, it's getting dangerously close..How about the classic `<img src=x onerror=alert(1)>`?
- ▪An `<img>` tag with an event handler is rendered, which fires without additional user interaction2.
Hacker News (AI / LLM) files mainly under ai. We currently carry 4,272 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Positive |
| Canonical URL | https://positive.security/blog/banking-ai-xss |
| Publication time | Mon, 10 Aug 2026 12:51:14 +0000 |
| Retrieval time | 2026-08-10T13:00:44.951Z |
| Last seen | 2026-08-10T13:00:44.951Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | Jr22ZV06dGaj · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
-- MARKDOWN --- Our bank introduced an **AI chatbot** that can access customer data and trigger actions- We found it **vulnerable to XSS** and created PoCs to deliver the payload via an **uploaded PDF** and **bank transaction references**- A **victim asking the chatbot** to "list this month's transactions" can trigger the XSS and **compromise their banking session**- We **responsibly disclosed** the issue, and a **fix was quickly deployed**# Table of Contents- [Discovery](#discovery)- ["Weaponizing" the XSS](#weaponizing-the-xss)- [Finding better attack vectors](#finding-better-attack-vectors) - [Invoice PDF](#invoice-pdf) - [Bank transfer](#bank-transfer)- [Disclosure](#disclosure)- [Conclusion](#conclusion)# DiscoveryWhile trying out the new AI feature of our business bank to find a…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Positive.