dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-0856

HIGH · 7.3 CVSS v3.1 Published 2025-05-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
The PGS Core plugin for WordPress is vulnerable to unauthorized access, modification, and loss of data due to a missing capability check on multiple functions in all versions up to, and including, 5.8.0. This makes it possible for unauthenticated attackers to add, modify, or plugin options.

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

The PGS Core WordPress plugin up to version 5.8.0 lacks capability checks on multiple functions, allowing unauthenticated attackers to add, modify, or delete plugin options via direct API calls. This broken access control vulnerability enables complete control over plugin settings without any authentication.

MitigationUpdate to version 5.8.1 or later which includes proper capability checks. If no update is available, disable the plugin until a patched version is released.

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
Low
Integrity
Low
Availability
Low

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

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. Verify PGS Core plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'PGS Core' in the list, or check the plugins directory via file system for /wp-content/plugins/pgs-core/
    Affected if PGS Core plugin is present in the WordPress installation
  2. Check installed version number
    In WordPress admin, find PGS Core in the Plugins list and read the version number displayed below the plugin name. Alternatively, check the main plugin file header in /wp-content/plugins/pgs-core/ for the 'Version' tag
    Affected if Version is 5.8.0 or lower (any version below 5.8.1)
  3. Confirm plugin is active
    In WordPress admin Plugins page, verify that PGS Core shows as 'Active' under the plugin status
    Affected if Plugin is active and version is 5.8.0 or lower

If the PGS Core WordPress plugin is installed, active, and running version 5.8.0 or lower, the environment is affected by CVE-2025-0856 and allows unauthenticated modification of plugin options.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 5.8.1 or later which includes proper capability checks. If no update is available, disable the plugin until a patched version is released.

Recommended fix Moderate confidence

Upgrade to PGS Core version 5.8.1 or later (the first version containing the security fix)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the PGS Core plugin in the list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin is running version 5.8.1 or higher
  6. 6. Test critical site functionality to ensure the update did not break existing features
Caveat Review plugin settings after upgrade as default configurations may have changed

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0856 — 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-2025-0856 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