CVE-2018-25058
CVE-2018-25058 is a medium-severity vulnerability in Twitter-post-fetcher Project Twitter-post-fetcher with a CVSS 3.x base score of 4.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-1022.
Key facts
- Severity: Medium (CVSS 3.x base score 4.2)
- EPSS exploit prediction: 1% (40th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-1022
- Affected product: Twitter-post-fetcher Project Twitter-post-fetcher
- Published:
- Last modified:
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.
Frequently asked questions
- What is CVE-2018-25058?
- 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.
- How severe is CVE-2018-25058?
- CVE-2018-25058 has a CVSS 3.x base score of 4.2, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and user interaction. Impact on confidentiality is none, integrity low, and availability low.
- Is CVE-2018-25058 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (40th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2018-25058?
- CVE-2018-25058 affects Twitter-post-fetcher Project Twitter-post-fetcher. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2018-25058?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- When was CVE-2018-25058 published?
- CVE-2018-25058 was published on 2022-12-29 and last updated on 2026-06-17.
References
- https://github.com/jasonmayes/Twitter-Post-Fetcher/commit/7d281c6fb5acbc29a2cad295262c1f0c19ca56f3
- https://github.com/jasonmayes/Twitter-Post-Fetcher/pull/170
- https://github.com/jasonmayes/Twitter-Post-Fetcher/releases/tag/18.0.0
- https://vuldb.com/?ctiid.217017
- https://vuldb.com/?id.217017
Affected products (1)
- cpe:2.3:a:twitter-post-fetcher_project:twitter-post-fetcher:*:*:*:*:*:*:*:*
Other CWE-1022 vulnerabilities
- CVE-2022-1583 — Medium (CVSS 6.5): The External Links in New Window / New Tab WordPress plugin before 1.43 does not ensure window.opener is set to "null"…
- CVE-2020-36624 — Medium (CVSS 6.3): A vulnerability was found in ahorner text-helpers up to 1.0.x. It has been declared as critical. This vulnerability…
- CVE-2024-39727 — Medium (CVSS 6.1): IBM Engineering Lifecycle Optimization - Engineering Insights 7.0.2 and 7.0.3 uses a web link with untrusted…
- CVE-2022-4927 — Medium (CVSS 5.5): A vulnerability was found in ualbertalib NEOSDiscovery 1.0.70 and classified as problematic. This issue affects some…
- CVE-2025-33014 — Medium (CVSS 5.4): IBM Sterling B2B Integrator and IBM Sterling File Gateway 6.0.0.0 through 6.1.2.7 and 6.2.0.0 through 6.2.0.4 uses a…
- CVE-2022-2600 — Medium (CVSS 5.4): The Auto-hyperlink URLs WordPress plugin through 5.4.1 does not set rel="noopener noreferer" on generated links, which…