LiveActive security incident?Get immediate response
CVE Record

CVE-2018-25058: Twitter-Post-Fetcher Link Target twitterFetcher.js reverse tabnabbing

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.

MediumCVSS 4.2Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This affects websites using Twitter-Post-Fetcher 17.x or earlier. Links generated by the component may let a newly opened untrusted page retain access to the original page through window.opener. A user must click a link, and impact is limited, but affected public pages should be updated.

Executive priority

Treat this as a moderate web hygiene issue, not an emergency. Remediate during the next web dependency maintenance cycle, sooner for high-traffic public pages where brand trust or user redirection risk matters.

Technical view

CVE-2018-25058 is a reverse tabnabbing issue in js/twitterFetcher.js Link Target Handler in Twitter-Post-Fetcher up to 17.x. The CVSS 3.1 score is 4.2 with network attack vector, high complexity, no privileges, and required user interaction. Version 18.0.0 and commit 7d281c6fb5acbc29a2cad295262c1f0c19ca56f3 address it.

Likely exposure

Exposure is likely limited to sites or applications that embed Twitter-Post-Fetcher 17.x or earlier and render external links from that component. The bundle provides no CPEs or downstream product list, so asset discovery must focus on dependency and static-file inventory.

Exploitation context

The sources describe remote initiation but require user interaction. The issue depends on a user opening an untrusted target from an affected page. The bundle does not cite CISA KEV listing, active exploitation, public exploit code, or observed attacks.

Researcher notes

Evidence is strongest for the affected component, version range, CVSS, and fixed release. The affected code path is described only as an unknown part of js/twitterFetcher.js Link Target Handler. No source in the bundle establishes exploitation in the wild.

Mitigation direction

  • Upgrade Twitter-Post-Fetcher to version 18.0.0 or later.
  • Prioritize public pages using Twitter-Post-Fetcher 17.x or earlier.
  • If upgrade is delayed, check vendor guidance for link-hardening options.
  • Retest pages after upgrading to confirm the fixed script is served.

Validation and detection

  • Search dependency manifests and static assets for Twitter-Post-Fetcher versions.
  • Inspect deployed pages for js/twitterFetcher.js from affected releases.
  • Confirm the deployed package or script matches version 18.0.0 or later.
  • Review external-link behavior for window.opener protections after remediation.
Prepared
Confidence
high
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-1022: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-25058 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.2CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:L1.62.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.2Medium
CVSS 3.1 vector shape for CVE-2018-25058Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aTwitter-Post-Fetcher17.xListed
Weakness

CWE details

CWE-1022

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-1022 · source CWE mapping

Use of Web Link to Untrusted Target with window.opener Access

Use of Web Link to Untrusted Target with window.opener Access represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs