dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-32507

HIGH · 7.3 CVSS v3.1 Published 2024-12-13
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
Missing Authorization vulnerability in wp3sixty Woo Custom Emails allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Woo Custom Emails: from n/a through 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 confidence

Missing authorization vulnerability in the Woo Custom Emails WordPress plugin allows unauthenticated or unauthorized users to access administrative functions or modify email configurations due to incorrectly configured access control security levels. The plugin fails to properly verify user capabilities before allowing access to sensitive actions.

MitigationUpdate to the latest patched version of Woo Custom Emails. If no patch is available, disable the plugin or restrict access to admin functions at the web server level until a fix 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. Locate the Woo Custom Emails plugin
    Navigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and search for 'Woo Custom Emails' or check the wp-content/plugins directory for a folder named 'woo-custom-emails'
    Affected if The plugin is installed and active
  2. Identify the installed version
    In the WordPress plugins list, locate Woo Custom Emails and read the version number displayed beneath the plugin name. Alternatively, open the main plugin PHP file and look for the 'Version' header in the plugin comments
    Affected if The version is lower than the patched version (compare against the vendor's release notes for the security fix)
  3. Verify admin function accessibility
    Attempt to access the plugin's admin pages or endpoints directly via URL without logging in or with a low-privilege user account. Common paths include /wp-admin/admin.php?page=woo-custom-emails or similar plugin-specific URLs
    Affected if Administrative pages load or return non-error responses without proper authentication or capability checks
  4. Check for exposed email configuration actions
    Inspect the plugin's AJAX handlers or form actions by viewing page source on plugin admin pages, then test those action endpoints with unauthenticated requests using a tool like curl
    Affected if Sensitive actions like saving or modifying email templates complete successfully without requiring admin-level capabilities

A user is affected if Woo Custom Emails is installed and the installed version lacks the authorization fix, allowing unauthorized access to admin functions or email configuration changes.

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 the latest patched version of Woo Custom Emails. If no patch is available, disable the plugin or restrict access to admin functions at the web server level until a fix is released.

Recommended fix Low confidence

Version 2.3 or later (the first fixed release after the affected version 2.2)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Woo Custom Emails' plugin by wp3sixty
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. If no update is shown, manually download the latest version from the WordPress plugin repository or the vendor's website
  6. 6. After updating, verify the plugin is running on version 2.3 or later
  7. 7. Test the email customization functionality to ensure the plugin works correctly after the update
Caveat Unknown - review the plugin changelog for any breaking changes between 2.2 and the fixed release

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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