CVE-2010-1040 json
The "IP address range limitation" function in OpenPNE 1.6 through 1.8, 2.0 through 2.8, 2.10 through 2.14, and 3.0 through 3.4, when mobile…
published 16y ago modified 4mo ago also EUVD-2010-1072
- cvss
- 5.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 65%
- public exploits
- 0
- none known
Summary
The "IP address range limitation" function in OpenPNE 1.6 through 1.8, 2.0 through 2.8, 2.10 through 2.14, and 3.0 through 3.4, when mobile device support is enabled, allows remote attackers to bypass the "simple login" functionality via unknown vectors related to spoofing.
Is CVE-2010-1040 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.07% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:P/I:P/A:N |
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
openpne.jp
/archives/4612/
vendor-advisory
-
secunia.com
/advisories/38857
third-party-advisory, vendor-advisory
- ipa.go.jp /security/vuln/alert/201003_openpne.html
-
jvndb.jvn.jp
/ja/contents/2010/JVNDB-2010-000006.html
third-party-advisory
-
jvn.jp
/en/jp/JVN06874657/index.html
third-party-advisory
Sources
- CVE List CVE-2010-1040
- NVD CVE-2010-1040
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.