CVE-2010-2669 json
Cross-site scripting (XSS) vulnerability in admin/editors/text/editor-body.php in Orbis CMS 1.0.2 allows remote attackers to inject arbitra…
published 16y ago modified 4mo ago also EUVD-2010-2673
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.5%
- EPSS 1.5% chance of exploitation in 30 days, percentile 74%
- public exploits
- 1
- Exploit-DB
Summary
Cross-site scripting (XSS) vulnerability in admin/editors/text/editor-body.php in Orbis CMS 1.0.2 allows remote attackers to inject arbitrary web script or HTML via the s parameter.
Is CVE-2010-2669 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (EDB-34253)
- Published
Exploit prediction
1.50% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-34253 Orbis CMS 1.0.2 - 'editor-body.php' Cross-Site Scripting webapps, 2010-07-05
- osvdb.org http://osvdb.org/66021 referenced PoC, tagged "exploit" by a source, unverified
- cross-site-scripting.blogspot.com http://cross-site-scripting.blogspot.com/2010/07/orbis-102-reflected-xss.html referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/41390 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
osvdb.org
/66021
vdb-entry, exploit
-
cross-site-scripting.blogspot.com
/2010/07/orbis-102-reflected-xss.html
exploit
-
securityfocus.com
/bid/41390
vdb-entry, exploit
-
secunia.com
/advisories/40474
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/60087
vdb-entry
Sources
- CVE List CVE-2010-2669
- NVD CVE-2010-2669
Fencer Intel 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.