CVE-2025-60130
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 · uneditedMissing Authorization vulnerability in wedos.com WEDOS Global wgpwpp allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects WEDOS Global: from n/a through <= 1.2.2.
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 confidenceMissing authorization vulnerability in WEDOS Global wgpwpp allows unauthenticated or unauthorized users to access functionality that should be constrained by Access Control Lists (ACLs). This is a broken access control issue where certain functions or endpoints do not properly verify user permissions before granting access to sensitive operations or data.
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
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if WEDOS Global wgpwpp is installedCheck your WordPress installation's wp-content/plugins directory for a folder named 'wgpwpp' or search for 'WEDOS Global' in the WordPress plugin admin interface under Plugins.Affected if The wgpwpp plugin folder exists in the plugins directory.
-
Determine the installed version of wgpwppOpen the main plugin file (usually wp-content/plugins/wgpwpp/wgpwpp.php or similar) and locate the version comment/constant at the top of the file, or check the WordPress plugin admin panel which displays the installed version.Affected if The plugin is installed and returns a version number that matches any vulnerable release of wgpwpp.
-
Inspect exposed endpoints and functionsReview the plugin's PHP files for action/filter hooks registered with add_action or add_callback, and identify any AJAX endpoints (wp_ajax_*) or REST API routes (register_rest_route) that the plugin registers.Affected if The plugin registers public-facing endpoints or functions that perform sensitive operations without checking user capabilities.
-
Test for unauthenticated access to sensitive functionsUsing a tool like curl or Burp Suite, attempt to access the identified plugin endpoints without providing authentication credentials (cookies, tokens) and observe whether the requests succeed.Affected if Requests to sensitive plugin functions complete successfully without requiring valid authentication or authorization.
-
Verify ACL enforcement on plugin functionalityExamine the plugin source code for current_user_can, wp_get_current_user, or similar authorization checks before executing sensitive operations in each identified endpoint.Affected if The plugin code lacks proper capability checks (like current_user_can) before executing sensitive functions.
A user is affected if the WEDOS Global wgpwpp plugin is installed, exposes endpoints accessible without authentication, and lacks authorization checks (such as current_user_can) before performing sensitive operations.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper authorization checks on all sensitive endpoints and functions to verify user permissions before allowing access. Ensure ACLs are correctly defined and enforced across all application functionality.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60130 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-60130 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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