CVE-2026-8905 json
Osiris Signature Banner <= 0.5 - Cross-Site Request Forgery to Stored Cross-Site Scripting via 'prepend_text' Parameter
published 2026-06-24 4 mo ago modified 2026-06-25 4 mo ago also EUVD-2026-38655
- cvss
- 6.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
The Osiris Signature Banner plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 0.5. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4 mo ago
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected products
- osiris8 Osiris Signature Banner
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/03226722-000c-4bfe-a09b-e75882274845?source=cve
- plugins.trac.wordpress.org /browser/osiris-signature-banner/tags/0.5/osiris-signature-banner.php#L118
- plugins.trac.wordpress.org /browser/osiris-signature-banner/tags/0.5/osiris-signature-banner.php#L189
- plugins.trac.wordpress.org /browser/osiris-signature-banner/tags/0.5/osiris-signature-banner.php#L107
- plugins.trac.wordpress.org /browser/osiris-signature-banner/tags/0.5/osiris-signature-banner.php#L139
Sources
- CVE List CVE-2026-8905
- NVD CVE-2026-8905
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.