CVE-2018-25058: A vulnerability classified as problematic has been found in Twitter-Post-Fetcher up to 17.x

Q: How do I fix CVE-2018-25058?

twitter-post-fetcher: upgrade to 18.0.0. Exact commands for each OS are on this page.

Q: Is CVE-2018-25058 being exploited?

CVE-2018-25058 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2018-25058 affect?

CVE-2018-25058 affects twitter-post-fetcher. Severity is medium (CVSS 4.2). 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 un

Q: How urgent is CVE-2018-25058?

Priority 26/100. No elevated risk signals yet.

Routine

MEDIUM 4.2UPGRADE

CVE-2018-25058 is a medium-severity flaw (CVSS 4.2) affecting twitter-post-fetcher. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 7d281c6fb5acbc29a2cad295262c1f0c19ca

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.2 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.6% (top 53%)
CISA exploited list	No
Weakness	CWE-1022
Published	2022-12-29
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: twitter-post-fetcher project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-12-29 08:15 UTCPublished CVE record published
2026-06-17 01:54 UTCUpdated Record last modified

twitter-post-fetcher project twitter-post-fetcher UPGRADE

Affected: < 18.0.0

Fixed in: 18.0.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy twitter-post-fetcher || rpm -q twitter-post-fetcher || twitter-post-fetcher --version

2. UPGRADE to 18.0.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade twitter-post-fetcher

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade twitter-post-fetcher

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-25058?

twitter-post-fetcher: upgrade to 18.0.0. Exact commands for each OS are on this page.

Is CVE-2018-25058 being exploited?

CVE-2018-25058 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-25058 affect?

CVE-2018-25058 affects twitter-post-fetcher. Severity is medium (CVSS 4.2). 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 un

How urgent is CVE-2018-25058?

Priority 26/100. No elevated risk signals yet.

References

← Back to latest CVEs