dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-12980

HIGH · 7.5 CVSS v3.1 Published 2025-12-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/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 Post Grid Gutenberg Blocks for News, Magazines, Blog Websites – PostX plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the '/ultp/v2/get_dynamic_content/' REST API endpoint in all versions up to, and including, 5.0.3. This makes it possible for unauthenticated attackers to retrieve sensitive user metadata, including password hashes.

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 · high confidence

The PostX WordPress plugin has a missing capability check on the `/ultp/v2/get_dynamic_content/` REST API endpoint, allowing unauthenticated attackers to retrieve sensitive user metadata including password hashes. This is a broken access control vulnerability where the REST API endpoint does not verify user permissions before returning data.

MitigationAdd a capability check (such as `current_user_can('edit_posts')` or similar appropriate capability) to the REST API endpoint `/ultp/v2/get_dynamic_content/` to ensure only authorized users can access user metadata. Alternatively, update to the latest plugin version if a security patch is available.

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
None
Availability
None

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

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 PostX plugin is installed
    Navigate to WordPress Admin > Plugins and verify PostX plugin is installed and active
    Affected if PostX plugin is present and active in the WordPress installation
  2. Identify installed PostX version
    Go to Plugins > Installed Plugins > PostX and record the version number. Compare this against the version that includes the security patch (check plugin changelog or security advisory for the fixed version)
    Affected if Running a version prior to the patched release
  3. Test unauthenticated REST API access
    Send a GET request to /wp-json/ultp/v2/get_dynamic_content/ using curl or a browser without providing any authentication credentials
    Affected if The endpoint responds with HTTP 200 and returns data without requiring login
  4. Verify sensitive data exposure
    Examine the API response payload. Look for user metadata fields such as password hashes, user emails, or other sensitive user information
    Affected if The endpoint returns user metadata including password hashes to unauthenticated requests

If the /ultp/v2/get_dynamic_content/ endpoint is accessible without authentication and returns user metadata such as password hashes, the environment is affected by this vulnerability.

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

Add a capability check (such as `current_user_can('edit_posts')` or similar appropriate capability) to the REST API endpoint `/ultp/v2/get_dynamic_content/` to ensure only authorized users can access user metadata. Alternatively, update to the latest plugin version if a security patch is available.

Recommended fix High confidence

PostX version 5.0.4 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'PostX' (Post Grid Gutenberg Blocks) in the plugin list
  4. If an update is available, click 'Update Now' to update to the latest version (5.0.4 or higher)
  5. Alternatively, download the latest version from wordpress.org/plugins/post-grid-gutenberg-blocks/ and upload it manually via Plugins > Add New > Upload Plugin
  6. After updating, verify the REST API endpoint '/ultp/v2/get_dynamic_content/' is no longer accessible without authentication

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-12980 — 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-12980 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