CVE-2019-15012 [High] | Privilege Escalation in Bitbucket

Bitbucket Server and Bitbucket Data Center from version 4.13. before 5.16.11, from version 6.0.0 before 6.0.11, from version 6.1.0 before 6.1.9, from version 6.2.0 before 6.2.7, from version 6.3.0 before 6.3.6, from version 6.4.0 before 6.4.4, from version 6.5.0 before 6.5.3, from version 6.6.0 before 6.6.3, from version 6.7.0 before 6.7.3, from version 6.8.0 before 6.8.2, from version 6.9.0 before 6.9.1 had a Remote Code Execution vulnerability via the edit-file request. A remote attacker with write permission on a repository can write to any arbitrary file to the victims Bitbucket Server or Bitbucket Data Center instance using the edit-file endpoint, if the user has Bitbucket Server or Bitbucket Data Center running, and has the permission to write the file at that destination. In some cases, this can result in execution of arbitrary code by the victims Bitbucket Server or Bitbucket Data Center instance.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	1.82%	1.60%	-0.23%
2	2026-04-21	1.92%	1.82%	-0.10%
3	2025-11-21	—	1.92%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

1.82%

1.60%

-0.23%

2026-04-21

1.92%

1.82%

-0.10%

2025-11-21

—

1.92%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
8.8	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	2.8	5.9	[email protected]
6.5	2.0	MEDIUM	`AV:N/AC:L/Au:S/C:P/I:P/A:P` Click to expand Access vector (AV:N) Can be exploited remotely over network reachability. Access complexity (AC:L) Exploitation conditions are straightforward and predictable. Authentication (AU:S) A single authentication is required. Confidentiality impact (C:P) Partial confidentiality impact. Integrity impact (I:P) Partial integrity impact. Availability impact (A:P) Partial availability impact.	8.0	6.4	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

8.8

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

2.8

5.9

[email protected]

6.5

2.0

MEDIUM

AV:N/AC:L/Au:S/C:P/I:P/A:P Click to expand

Access vector (AV:N): Can be exploited remotely over network reachability.
Access complexity (AC:L): Exploitation conditions are straightforward and predictable.
Authentication (AU:S): A single authentication is required.
Confidentiality impact (C:P): Partial confidentiality impact.
Integrity impact (I:P): Partial integrity impact.
Availability impact (A:P): Partial availability impact.

8.0

6.4

[email protected]

Affected software / configurations for CVE-2019-15012

Vendor	Product	Version	Raw CPE
atlassian	bitbucket	>= 4.13.0, < 5.6.11	cpe:2.3:a:atlassian:bitbucket::::::::
atlassian	bitbucket	>= 6.0.0, < 6.0.11	cpe:2.3:a:atlassian:bitbucket::::::::
atlassian	bitbucket	>= 6.1.0, < 6.1.9	cpe:2.3:a:atlassian:bitbucket::::::::
atlassian	bitbucket	>= 6.2.0, < 6.2.7	cpe:2.3:a:atlassian:bitbucket::::::::
atlassian	bitbucket	>= 6.3.0, < 6.3.6	cpe:2.3:a:atlassian:bitbucket::::::::
atlassian	bitbucket	>= 6.4.0, < 6.4.4	cpe:2.3:a:atlassian:bitbucket::::::::
atlassian	bitbucket	>= 6.5.0, < 6.5.3	cpe:2.3:a:atlassian:bitbucket::::::::
atlassian	bitbucket	>= 6.6.0, < 6.6.3	cpe:2.3:a:atlassian:bitbucket::::::::
atlassian	bitbucket	>= 6.7.0, < 6.7.3	cpe:2.3:a:atlassian:bitbucket::::::::
atlassian	bitbucket	>= 6.8.0, < 6.8.2	cpe:2.3:a:atlassian:bitbucket::::::::
atlassian	bitbucket	>= 6.9.0, < 6.9.1	cpe:2.3:a:atlassian:bitbucket::::::::

References for CVE-2019-15012

URL	Tags
https://jira.atlassian.com/browse/BSERV-12100	Issue Tracking Vendor Advisory

URL

CVE-2019-15012

Exploit prediction scoring system (EPSS) score for CVE-2019-15012

Common vulnerability scoring system (CVSS) metrics for CVE-2019-15012

Weakness enumeration for CVE-2019-15012

Affected software / configurations for CVE-2019-15012

References for CVE-2019-15012