CVE-2014-7292 json
Open redirect vulnerability in the Click-Through feature in Newtelligence dasBlog 2.1 (2.1.8102.813), 2.2 (2.2.8279.16125), and 2.3 (2.3.90…
published 12y ago modified 4mo ago also EUVD-2014-7163
- cvss
- 5.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 80%
- public exploits
- 0
- none known
Summary
Open redirect vulnerability in the Click-Through feature in Newtelligence dasBlog 2.1 (2.1.8102.813), 2.2 (2.2.8279.16125), and 2.3 (2.3.9074.18820) allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in the url parameter to ct.ashx.
Is CVE-2014-7292 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.97% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- tetraph.com http://www.tetraph.com/blog/cves/cve-2014-7292-newtelligence-dasblog-open-redirect-vulnerability referenced PoC, tagged "exploit" by a source, unverified
- seclists.org http://seclists.org/fulldisclosure/2014/Oct/91 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/128749/Newtelligence-dasBlog-2.3-Open-Redirect.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:P/I:P/A:N |
References
-
tetraph.com
/blog/cves/cve-2014-7292-newtelligence-dasblog-open-redirect-vulnerability
exploit
-
seclists.org
/fulldisclosure/2014/Oct/91
mailing-list, exploit
-
packetstormsecurity.com
/files/128749/Newtelligence-dasBlog-2.3-Open-Redirect.html
exploit
-
securityfocus.com
/bid/70654
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/97667
vdb-entry
Sources
- CVE List CVE-2014-7292
- NVD CVE-2014-7292
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.