Research / Finding
WKWebView payment bridge accepts payment_form_submit from untrusted subframes without frame validation
F-TELEGRAM-IOS-BOTPAY-001
Public snapshot: 26 Sep 2026. Status, releases and attribution belong to each source below; none is inferred from another record.
Read the evidence · View in research browse
Recorded evidence
—score not recorded
WKWebView payment bridge accepts payment_form_submit from untrusted subframes without frame validation
fixed publicly
details
- Finding IDs
- F-TELEGRAM-IOS-BOTPAY-001
- Status
- fixed publicly
- Reported via
- Telegram security contact
- Note
- accepted as LOW. public fix commit a8a308d7a6843cb41e4e0e76908e552a4aeb1ee9 on 2026-02-13 switches the payment bridge script to forMainFrameOnly: true; the fix is present in release-12.5.
F-TELEGRAM-IOS-BOTPAY-001: Access control. Payment user scripts are injected into frames outside the intended main-frame boundary. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.
Mechanism source for F-TELEGRAM-IOS-BOTPAY-001
Security area (1seal assessment): Authorization. Payment user scripts are injected into frames outside the intended main-frame boundary. Reviewed 24 Sep 2026.
Clarify or correct this record privately. The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy.
How this page groups evidence
This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules.