dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-60127

MEDIUM · 5.4 CVSS v3.1 Published 2025-09-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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
Missing Authorization vulnerability in ArtistScope CopySafe Web Protection wp-copysafe-web allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects CopySafe Web Protection: from n/a through <= 5.1.

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

Missing authorization vulnerability in the CopySafe Web Protection WordPress plugin (wp-copysafe-web) allows attackers to exploit incorrectly configured access control security levels. This broken access control issue enables unauthorized access to protected functionality or content that should require proper authentication and authorization checks.

MitigationAudit and implement proper authorization checks across all plugin endpoints; if no vendor patch is available, disable and replace the plugin with a secure alternative.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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. Check if CopySafe Web Protection plugin is installed
    Navigate to wp-content/plugins/ directory and look for a folder named 'wp-copysafe-web' or 'copysafe-web'. Alternatively, check the WordPress admin dashboard under Plugins > Installed Plugins for an entry named 'CopySafe Web Protection' or similar.
    Affected if The plugin folder exists in wp-content/plugins/ or the plugin appears in the WordPress plugins list
  2. Determine the installed plugin version
    Open the main plugin file (typically wp-copysafe-web.php) in the plugin directory and locate the 'Version' header in the plugin comment block at the top of the file. Alternatively, check the readme.txt file for the version number.
    Affected if The version cannot be determined or is lower than any patched version provided by the vendor
  3. Verify the plugin is active
    Check WordPress admin > Plugins > Installed Plugins to confirm whether CopySafe Web Protection shows as 'Active'. Also check the site directly if admin access is unavailable.
    Affected if The plugin is activated on the WordPress site
  4. Inspect access control security settings
    Access the plugin settings page in WordPress admin (usually under Settings > CopySafe Web or a dedicated menu item). Look for security level, access control, or permission settings related to content protection features. Examine any configuration options that control who can access protected content or plugin functions.
    Affected if Security level settings are configured to a level that permits unauthenticated or unauthorized access, or if the plugin exposes protected functionality without requiring authentication

A user is affected if the CopySafe Web Protection plugin is installed, active, and has access control security levels configured in a way that allows unauthorized access to protected functionality.

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

Audit and implement proper authorization checks across all plugin endpoints; if no vendor patch is available, disable and replace the plugin with a secure alternative.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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