WeSearch

Banking AI XSS: The exploit is in the payment reference

·6 min read · 0 reactions · 0 comments · 2 views
Banking AI XSS: The exploit is in the payment reference
TL;DR · WeSearch summary

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.

Key facts
About this source

Hacker News (AI / LLM) files mainly under ai. We currently carry 4,272 of its stories.

Original article
Positive
Read full at Positive →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

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 publisherPositive
Canonical URLhttps://positive.security/blog/banking-ai-xss
Publication timeMon, 10 Aug 2026 12:51:14 +0000
Retrieval time2026-08-10T13:00:44.951Z
Last seen2026-08-10T13:00:44.951Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterJr22ZV06dGaj · 1 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

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.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from Positive