LiveActive security incident?Get immediate response
CVE Record

CVE-2021-39339: Telefication <= 1.8.0 Open Proxy and Server-Side Request Forgery

The Telefication WordPress plugin is vulnerable to Open Proxy and Server-Side Request Forgery via the ~/bypass.php file due to a user-supplied URL request value that gets called by a curl requests. This affects versions up to, and including, 1.8.0.

MediumCVSS 5.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Telefication for WordPress up to version 1.8.0 can be misused as an open proxy through its bypass.php file. An attacker may cause the website server to make outbound requests to attacker-chosen URLs. The public sources do not show active exploitation or name a fixed release.

Executive priority

Treat this as a moderate web-platform hygiene issue. Prioritize internet-facing WordPress sites and shared hosting environments, but do not escalate as actively exploited based on the provided evidence.

Technical view

CVE-2021-39339 is a CWE-918 SSRF/open proxy issue in Telefication <=1.8.0. A user-supplied URL request value in bypass.php is passed to curl. CVSS 3.1 is 5.8: network reachable, low complexity, no privileges, no user interaction, changed scope, and low availability impact.

Likely exposure

Exposure is limited to WordPress sites with the Telefication plugin installed at version 1.8.0 or earlier, especially where bypass.php remains web-accessible. The bundle provides no CPEs or broader affected product list.

Exploitation context

The source bundle says this CVE is not in CISA KEV, and no cited source states active exploitation. The practical risk is proxy abuse or SSRF-style outbound requests from the WordPress server, not confirmed data theft or code execution.

Researcher notes

The strongest evidence is the CVE description, Wordfence advisory reference, and WordPress plugin Trac source path. No patch version, exploitation evidence, or detailed vendor mitigation is included, so avoid asserting a fixed release or exploit activity.

Mitigation direction

  • Inventory WordPress sites for Telefication plugin version 1.8.0 or earlier.
  • Disable or remove affected Telefication installs until vendor guidance confirms a safe version.
  • Check Wordfence and WordPress plugin sources for current remediation guidance.
  • Limit unnecessary outbound network access from WordPress hosting environments.
  • Monitor web server logs for requests to Telefication bypass.php.

Validation and detection

  • Confirm whether Telefication is installed on each WordPress site.
  • Record the installed plugin version and flag versions up to 1.8.0.
  • Check whether wp-content/plugins/telefication/bypass.php exists on the host.
  • Review access logs for requests targeting the plugin bypass.php file.
  • Review egress logs for unexpected outbound requests from WordPress servers.
Prepared
Confidence
high
Sources
4

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 · medium confidence lookup

CWE-918: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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
description · low confidence lookup

Cloud metadata behavior lookup

The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-39339 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
5.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/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
3Source 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
5.8CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:L3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.8Medium
CVSS 3.1 vector shape for CVE-2021-39339Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
TeleficationTelefication1.8.0Listed
Weakness

CWE details

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

CWE-918 · source CWE mapping

Server-Side Request Forgery (SSRF)

Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.