LiveActive security incident?Get immediate response
CVE Record

CVE-2020-15734: Same-origin policy vulnerability in Bitdefender Safepay

An Origin Validation Error vulnerability in Bitdefender Safepay allows an attacker to manipulate the browser's file upload capability into accessing other files in the same directory or sub-directories. This issue affects: Bitdefender Safepay versions prior to 25.0.7.29.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Bitdefender Safepay had a same-origin policy flaw that could let an attacker trick its file upload behavior into accessing nearby files. The main business concern is confidentiality: sensitive local files could be exposed if a user interacts with the attack path on an affected endpoint.

Executive priority

Treat this as a targeted confidentiality risk, not an internet-scale emergency. Patch affected Safepay endpoints through normal endpoint security update processes, with priority for users handling financial, personal, or sensitive local documents.

Technical view

CVE-2020-15734 is a CWE-346 Origin Validation Error in Bitdefender Safepay before 25.0.7.29. CVSS 3.1 is 5.5: local attack vector, low complexity, no privileges, user interaction required, unchanged scope, high confidentiality impact, no integrity or availability impact.

Likely exposure

Exposure is limited to endpoints running Bitdefender Safepay versions earlier than 25.0.7.29. The source bundle does not identify affected operating systems, deployment configurations, or broader Bitdefender products beyond Safepay.

Exploitation context

The source bundle and KEV status do not support active exploitation. Exploitation requires local access and user interaction, which lowers broad remote risk, but successful abuse could expose files in the same directory or subdirectories accessible through the manipulated upload flow.

Researcher notes

Key evidence is limited to the CVE record and Bitdefender advisory. The vulnerability is an origin validation flaw affecting file access behavior. No public exploit status, workaround detail, affected OS matrix, or exploitation telemetry is included in the provided sources.

Mitigation direction

  • Upgrade Bitdefender Safepay to version 25.0.7.29 or later.
  • Check Bitdefender’s advisory for any product-specific remediation instructions.
  • Prioritize updates on systems handling sensitive local files.
  • Limit use of affected Safepay versions until patched.
  • Monitor vendor guidance for any newly published workarounds.

Validation and detection

  • Inventory endpoints for Bitdefender Safepay installations.
  • Confirm installed Safepay versions are 25.0.7.29 or later.
  • Flag any Safepay version earlier than 25.0.7.29 as affected.
  • Review endpoint management records for successful update completion.
  • Document remaining unpatched systems and ownership.
Prepared
Confidence
high
Sources
3

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-346: 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
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell 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-2020-15734 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.5 (3.1)
Known Exploited
No
Published

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

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
2Source 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.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N1.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2020-15734Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
BitdefenderSafepayunspecifiedListed
Weakness

CWE details

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

CWE-346 · source CWE mapping

Origin Validation Error

Origin Validation Error represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.