diaspora cross-site scripting in oEmbed endpoint via maxheight
- Exploited
- No known exploitation
- Fix
- Fixed in 0.10.0
- Who is exposed
- Not reported
Summary
The diaspora software has a cross-site scripting flaw in its oEmbed endpoint, where the maxheight parameter lets an attacker inject an onload handler into the returned HTML. An attacker can reach it remotely without logging in, and the script runs in third-party oEmbed consumers that embed the output unsanitized, though a user must take some action for it to trigger.
Written by a model
Original description
diaspora* before 0.10.0 contains a cross-site scripting vulnerability that allows unauthenticated attackers to inject iframe attributes via the maxheight parameter of the GET /oembed endpoint. Attackers can supply a single quote in maxheight to inject an onload handler into the returned html, executing script in third-party oEmbed consumers that embed it unsanitized.
What to do
Upgrade to a fixed version: 0.10.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133241 (diaspora before 0.10.0 XSS via maxheight in oEmbed endpoint), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133241 (entry last updated 2026-11-19):
Affected:
- diaspora diaspora: fixed in 0.10.0
Fixed versions: 0.10.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133241 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133241 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/diaspora/diaspora/releases/tag/v0.10.0
- https://github.com/diaspora/diaspora/commit/f3a7465aa2ec48a3057937c0c4c8d9aa48fba2d3
- https://github.com/diaspora/diaspora/blob/v0.9.1.0/app/helpers/posts_helper.rb#L22-L27
- https://github.com/diaspora/diaspora/blob/v0.9.1.0/app/controllers/posts_controller.rb#L35-L42
- https://github.com/diaspora/diaspora
- https://www.vulncheck.com/advisories/diaspora-before-0.10.0-xss-via-maxheight-in-oembed-endpoint
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133241
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133241"}.Affected versions
- diaspora diasporafixed in 0.10.0
cve.now Index
- Exploitation0/40No signal
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity2.3/10CVSS 2.3
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 24 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 8
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133241 |
| Record | NVD · CVE-2026-133241 |
| Other links 6 | |
| Advisory | GitHub · diaspora/diaspora · Release v0.10.0 |
| Patch | GitHub · diaspora/diaspora · Commit f3a7465a |
| Repository | GitHub · diaspora/diaspora · app/helpers/posts_helper.rb · L22-L27 |
| Repository | GitHub · diaspora/diaspora · app/controllers/posts_controller.rb · L35-L42 |
| Repository | GitHub · diaspora/diaspora · Repository |
| Link | vulncheck.com · advisories/diaspora-before-0.10.0-xss-via-maxheight-in-oembed-endpoint |
Questions about CVE-2026-133241
Is CVE-2026-133241 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-133241?
diaspora: before 0.10.0.
Source: cve.now feed data
How do I fix CVE-2026-133241?
Upgrade to a fixed version: 0.10.0.
Source: cve.now feed data
Related
- CVE-2026-133242diaspora before 0.10.0 Stored XSS via OpenGraph og:video:secure_url
- CVE-2026-131260Cross-Site Scripting (XSS) through the REST API in Splunk SOAR
- CVE-2026-131258Stored Cross-Site Scripting (XSS) through the REST API in Splunk SOAR
- CVE-2026-129327Apaczka.pl WooCommerce <= 1.4.8 - Unauthenticated Stored Cross-Site Scripting via '_apaczka' Parameter via Guest Checkout
- CVE-2026-131582PagBank / PagSeguro e Vindi para WooCommerce <= 5.1.6 - Unauthenticated Stored Cross-Site Scripting via 'customer.name' Parameter
- CVE-2026-120508Charitable <= 1.8.15.1 - Unauthenticated Stored Cross-Site Scripting via 'stripe_payment_method' Parameter
No corrections so far. Something wrong on this page? Report an error.