Skip to content
Noroxi
CVE-2019-12922· NVD / CVE Program· CNA mitre

A CSRF issue in phpMyAdmin 4.9.0.1 allows deletion of any server in the Setup page.

Noroxi assessment

Priority: Monitor (action score 29/100)

  • Public proof-of-concept code exists (Exploit-DB); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 10.6% (FIRST EPSS); higher than 95.7% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: phpmyadmin (Debian:12) 4:4.9.1+dfsg1-2; phpmyadmin/phpmyadmin (Packagist) 4.9.1; phpMyAdmin (SUSE:Package Hub 12) 4.9.1-bp151.3.6.1, 4.9.4-bp151.3.12.1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to phpmyadmin (Debian:12) 4:4.9.1+dfsg1-2; phpmyadmin/phpmyadmin (Packagist) 4.9.1; phpMyAdmin (SUSE:Package Hub 12) 4.9.1-bp151.3.6.1, 4.9.4-bp151.3.12.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

MediumCVSS 6.5 · v3.1—Proof of concept Fix available
Published
Sep 13, 2019
Updated
Jun 16, 2026
EPSS
10.6% · 95th percentile

Report tools

JSON

Action score

29

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
3 / 30 · 10.6%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2019-12922

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for phpmyadmin records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
phpmyadminphpmyadmin
fedoraprojectfedora

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • fedoraproject fedora29
  • fedoraproject fedora30
  • fedoraproject fedora31
  • phpmyadmin phpmyadminup to 4.9.0.1 inclusive

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12phpmyadminbefore 4:4.9.1+dfsg1-24:4.9.1+dfsg1-2
Packagistphpmyadmin/phpmyadminbefore 4.9.14.9.1
SUSE:Package Hub 12phpMyAdminbefore 4.9.1-bp151.3.6.14.9.1-bp151.3.6.1
SUSE:Package Hub 12phpMyAdminbefore 4.9.4-bp151.3.12.14.9.4-bp151.3.12.1
SUSE:Package Hub 12phpMyAdminbefore 4.9.1-bp151.3.6.14.9.1-bp151.3.6.1
SUSE:Package Hub 12phpMyAdminbefore 4.9.4-bp151.3.12.14.9.4-bp151.3.12.1

Same product

phpmyadmin: all records

Other highest-scoring records for the same primary product.

  • CVE-2009-1151Static code injection vulnerability in setup.php in phpMyAdmin 2.11.x before 2.11.9.5 and 3.x before 3.1.3.1 allows remote attackers to injeKEV
    98Now
  • CVE-2018-12613An issue was discovered in phpMyAdmin 4.8.x before 4.8.2, in which an attacker can include (view and potentially execute) files on the serve
    65This week
  • CVE-2016-5734phpMyAdmin 4.0.x before 4.0.10.16, 4.4.x before 4.4.15.7, and 4.6.x before 4.6.3 does not properly choose delimiters to prevent use of the p
    63This week

Published before and after this one in the same product

  • ← EarlierCVE-2019-11768Jun 5, 2019 · An issue was discovered in phpMyAdmin before 4.9.0.1.
    40Plan
  • ← EarlierCVE-2019-12616Jun 5, 2019 · An issue was discovered in phpMyAdmin before 4.9.0.
    32Monitor
  • Later →CVE-2019-18622Nov 22, 2019 · An issue was discovered in phpMyAdmin before 4.9.2.
    40Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:phpmyadmin4:4.9.1+dfsg1-2 · Debian:12Package registry (OSV)
opensuse:phpMyAdmin4.9.1-bp151.3.6.1 · openSUSE:Leap 15.0Package registry (OSV)
Packagist:phpmyadmin/phpmyadmin4.9.1Package registry (OSV)
suse:phpMyAdmin4.9.1-bp151.3.6.1 · SUSE:Package Hub 12Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Exploit-DB entry ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Exploit-DB entrywebapps2019-09-13

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. First PoCsame day
  2. Published
  3. TodayOct 22, 2026+2596 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
None
Integrity impact
High
Availability impact
None

Weakness class (CWE)

CWE-352 · Cross-Site Request Forgery (CSRF)

CVSS vector

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

nvd-primary

Root cause

State-changing requests rely on the session cookie the browser sends automatically; nothing verifies that the request came from the user’s own page.

The bug in code

The whole CWE-352 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
app.use(session({ cookie: { httpOnly: true } }));app.post("/account/address", updateAddress);

Fixed

ts
app.use(session({ cookie: { httpOnly: true, sameSite: "lax" } }));app.post("/account/address", csrfProtection, updateAddress);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records