dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-56030

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Unauthenticated Privilege Escalation in Paytium <= 5.0.2 versions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is an unauthenticated privilege escalation vulnerability in the Paytium WordPress plugin affecting versions 5.0.2 and below. An attacker without any authentication can escalate their privileges, potentially gaining administrator-level access to the WordPress site.

MitigationUpdate Paytium plugin to a version newer than 5.0.2. If immediate update is not possible, consider restricting access to the wp-admin area or disabling the plugin until the patch can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Paytium plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Paytium' in the list of installed plugins, or check the /wp-content/plugins/paytium directory exists on the server file system
    Affected if Paytium plugin is not installed on the WordPress site
  2. Identify the installed Paytium version
    In WordPress admin > Plugins > Installed Plugins > Click on Paytium plugin details to view the version number, or read the main plugin file header at /wp-content/plugins/paytium/paytium.php for the 'Version' field
    Affected if The displayed version number is 5.0.2 or lower
  3. Verify the vulnerability is exploitable
    This is an unauthenticated privilege escalation - check if the WordPress site allows external access to any Paytium-related AJAX endpoints or API routes. Inspect network traffic or check plugin PHP files for any action hooks that process requests without requiring authentication (such as 'wp_ajax_nopriv_*' or 'wp_ajax_*' actions handling user role or capability changes)
    Affected if Paytium is active and accessible to unauthenticated users, and the version is 5.0.2 or below

If Paytium plugin is installed and running version 5.0.2 or below with unauthenticated access to the site, the environment is affected by this CVE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Paytium plugin to a version newer than 5.0.2. If immediate update is not possible, consider restricting access to the wp-admin area or disabling the plugin until the patch can be applied.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-56030 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-56030 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data