CVE-2010-3931 json
Cross-site scripting (XSS) vulnerability in multiple Rocomotion products, including P board 1.18 and other versions, P forum 1.30 and earli…
published 15y ago modified 4mo ago also EUVD-2010-3909
- 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
- 0
- none known
Summary
Cross-site scripting (XSS) vulnerability in multiple Rocomotion products, including P board 1.18 and other versions, P forum 1.30 and earlier, P up board 1.38 and other versions, P diary R 1.13 and earlier, P link 1.11 and earlier, P link compact 1.04 and earlier, pplog 3.31 and earlier, pplog2 3.37 and earlier, PM bbs 1.07 and earlier, PM up bbs 1.08 and earlier, and PM forum 1.18 and earlier, allows remote attackers to inject arbitrary web script or HTML via unknown vectors.
Is CVE-2010-3931 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 FencerExploit prediction
1.52% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).
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
-
another.rocomotion.jp
/12949466953653.html
vendor-advisory
-
jvn.jp
/en/jp/JVN09115481/index.html
third-party-advisory
-
secunia.com
/advisories/42957
third-party-advisory, broken-link
-
jvndb.jvn.jp
/ja/contents/2011/JVNDB-2011-000006.html
third-party-advisory
-
securityfocus.com
/bid/45838
vdb-entry, third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/64745
vdb-entry, third-party-advisory
-
osvdb.org
/70495
vdb-entry, broken-link
Sources
- CVE List CVE-2010-3931
- NVD CVE-2010-3931
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.