dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2024-1308

HIGH · 7.5 CVSS v3.1 Published 2024-04-09
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 WooCommerce Cloak Affiliate Links plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'permalink_settings_save' function in all versions up to, and including, 1.0.33. This makes it possible for unauthenticated attackers to modify the affiliate permalink base, driving traffic to malicious sites via the plugin's affiliate links.

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 WooCommerce Cloak Affiliate Links plugin has a missing capability check on the 'permalink_settings_save' function, allowing unauthenticated attackers to modify the affiliate permalink base setting. This enables redirection of affiliate link traffic to attacker-controlled malicious sites.

MitigationUpdate the plugin to version 1.0.34 or later which includes proper capability checks on the permalink_settings_save function to restrict access to authorized administrators only.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Verify plugin installation
    Navigate to WordPress admin > Plugins and check if 'WooCommerce Cloak Affiliate Links' is installed and active
    Affected if The plugin is installed and active on the site
  2. Check installed plugin version
    In WordPress admin > Plugins, find the WooCommerce Cloak Affiliate Links plugin and note the version number displayed
    Affected if Version is lower than 1.0.34 (the version that includes the fix)
  3. Inspect plugin file for capability check
    Examine the plugin file containing the 'permalink_settings_save' function (typically in the main plugin PHP file). Look for a capability check like 'manage_options' or 'manage_woocommerce' before executing the function
    Affected if No capability check or nonce verification is found before the permalink_settings_save function executes
  4. Review affiliate permalink base setting
    Go to WordPress admin > Settings > Permalinks (or WooCommerce > Cloak Affiliate Links settings if available) and check the 'Affiliate Permalink Base' field for any unexpected values
    Affected if The permalink base is set to a URL you did not configure, or points to an unfamiliar domain

The site is affected if WooCommerce Cloak Affiliate Links plugin is installed with a version before 1.0.34 and the permalink_settings_save function lacks proper capability checks, allowing unauthenticated modification of affiliate link settings.

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 the plugin to version 1.0.34 or later which includes proper capability checks on the permalink_settings_save function to restrict access to authorized administrators only.

Recommended fix High confidence

Version 1.0.34 or later

  1. Update the WooCommerce Cloak Affiliate Links plugin to version 1.0.34 or later through the WordPress plugin repository
  2. Navigate to WordPress Admin > Plugins > Add New > Upload or update directly via Plugins page
  3. After updating, verify the permalink settings under the plugin's settings page to ensure they have not been tampered with
  4. Check that affiliate links are functioning correctly and redirecting to expected destinations
  5. Review the plugin settings for any unauthorized changes that may have occurred before the update
Caveat Review plugin changelog before upgrading to check for any configuration or feature changes

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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