iWorks Orphans unauthenticated stored XSS in comment content
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
The Orphans plugin for WordPress, from iworks, has a stored cross-site scripting flaw in how it handles comment content. An attacker can remotely, without logging in, inject scripts that run in the browser of any user who opens an affected page.
Written by a model
Original description
The Orphans plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 3.4.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires a two-step comment chain: a benign first comment must be approved under a given name and email so that WordPress's comment_previously_approved mechanism auto-publishes the attacker's payload comment without moderation.
Who should check
Sites and teams running the iworks Orphans WordPress plugin (sierotki) at versions before 3.4.6.
“Fixed Stored Cross-Site Scripting (XSS) via the comment parameter”
What to do
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-124216 (Orphans <= 3.4.5 - Unauthenticated Stored Cross-Site Scripting via Comment Content), 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-124216 (entry last updated 2026-11-21):
Affected:
- iworks Orphans: through 3.4.5
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-124216 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-124216 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://www.wordfence.com/threat-intel/vulnerabilities/id/d313cb15-59f4-4483-ba4b-d2237fa33248?source=cve
- https://plugins.trac.wordpress.org/browser/sierotki/tags/3.4.5/includes/iworks/class-iworks-orphan.php#L484
- https://plugins.trac.wordpress.org/browser/sierotki/tags/3.4.5/includes/iworks/class-iworks-orphan.php#L502
- https://plugins.trac.wordpress.org/browser/sierotki/tags/3.4.5/includes/iworks/class-iworks-orphan.php#L572
- https://plugins.trac.wordpress.org/browser/sierotki/tags/3.4.5/includes/iworks/class-iworks-orphan.php#L266
- https://plugins.trac.wordpress.org/browser/sierotki/tags/3.4.5/wp-comments-post.php%20%28core%29
- https://github.com/iworks/sierotki/releases/tag/3.4.6
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-124216
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-124216"}.Affected versions
- iworks Orphansthrough 3.4.5
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.2/10CVSS 7.2
- No patch5/5No patch listed yet
What would change the score
- Would score about 74 if added to CISA KEV
- Would score about 69 if CISA's SSVC rates exploitation active
- Would score about 34 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 9
Questions about CVE-2026-124216
Is CVE-2026-124216 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-124216?
Orphans: through 3.4.5.
Source: cve.now feed data
Related
- CVE-2026-125791WordPress Orphans plugin <= 3.4.6 - Cross Site Scripting (XSS) vulnerability
- CVE-2025-12960Simple CSV Table <= 1.0.1 - Directory Traversal to Authenticated (Contributor+) Arbitrary File Read
- CVE-2024-8967PWA — easy way to Progressive Web App <= 1.6.3 - Authenticated (Author+) Stored Cross-Site Scripting via SVG File Upload
- CVE-2025-12538Fleet Manager <= 2.5.1 - Authenticated (Editor+) Stored Cross-Site Scripting
- CVE-2026-134262Admidio 5.0.0 before 5.0.18 Stored XSS via Role Name in Profile View
- CVE-2026-134250Grav Form Plugin 1.1.0 before 9.1.40 Stored XSS via Unsanitized File Uploads
No corrections so far. Something wrong on this page? Report an error.