CVE-2018-25058
Last modified
CVE-2018-25058 is a medium-severity vulnerability rated 6.1/10 on the CVSS scale. A vulnerability classified as problematic has been found in Twitter-Post-Fetcher up to 17.x. This affects an unknown part of the file js/twitterFetcher.js of the component Link Target Handler. EPSS estimates a 0.52% chance of exploitation in the next 30 days.
Description
A vulnerability classified as problematic has been found in Twitter-Post-Fetcher up to 17.x. This affects an unknown part of the file js/twitterFetcher.js of the component Link Target Handler. The manipulation leads to use of web link to untrusted target with window.opener access. It is possible to initiate the attack remotely. Upgrading to version 18.0.0 is able to address this issue. The name of the patch is 7d281c6fb5acbc29a2cad295262c1f0c19ca56f3. It is recommended to upgrade the affected component. The identifier VDB-217017 was assigned to this vulnerability.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Twitter-Post-Fetcher Project | Twitter-Post-Fetcher | < 18.0.0 |
References
- https://github.com/jasonmayes/Twitter-Post-Fetcher/commit/7d281c6fb5acbc29a2cad295262c1f0c19ca56f3Patch, Third Party Advisory
- https://github.com/jasonmayes/Twitter-Post-Fetcher/pull/170Third Party Advisory
- https://github.com/jasonmayes/Twitter-Post-Fetcher/releases/tag/18.0.0Third Party Advisory
- https://vuldb.com/?ctiid.217017Third Party Advisory
- https://vuldb.com/?id.217017Third Party Advisory
- https://github.com/jasonmayes/Twitter-Post-Fetcher/commit/7d281c6fb5acbc29a2cad295262c1f0c19ca56f3Patch, Third Party Advisory
- https://github.com/jasonmayes/Twitter-Post-Fetcher/pull/170Third Party Advisory
- https://github.com/jasonmayes/Twitter-Post-Fetcher/releases/tag/18.0.0Third Party Advisory
- https://vuldb.com/?ctiid.217017Third Party Advisory
- https://vuldb.com/?id.217017Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2018-25058?
How severe is CVE-2018-25058?
How do I fix CVE-2018-25058?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2018
- CVE-2018-25052A vulnerability has been found in Catalyst-Plugin-Session up…6.1
- CVE-2018-25053A vulnerability was found in moappi Json2html up to 1.1.x an…6.1
- CVE-2018-25054A vulnerability was found in shred cilla. It has been classi…5.4
- CVE-2018-25055A vulnerability was found in FarCry Solr Pro Plugin up to 1.…6.1
- CVE-2018-25056A vulnerability, which was classified as problematic, was fo…6.1
- CVE-2018-25057A vulnerability was found in simple_php_link_shortener. It h…9.8
- CVE-2018-25059A vulnerability was found in pastebinit up to 0.2.2 and clas…5.3
- CVE-2018-25060A vulnerability was found in Macaron csrf and classified as …7.5
- CVE-2018-25061A vulnerability was found in rgb2hex up to 0.1.5. It has bee…7.5
- CVE-2018-25062A vulnerability classified as problematic has been found in …7.5
- CVE-2018-25063A vulnerability classified as problematic was found in Zenos…6.1
- CVE-2018-25064A vulnerability was found in OSM Lab show-me-the-way. It has…6.1
Are you affected by CVE-2018-25058?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
