dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-2797

MEDIUM · 5.3 CVSS v3.1 Published 2024-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 MailerLite – Signup forms (official) plugin for WordPress is vulnerable to unauthorized plugin setting changes due to a missing capability check on the toggleRolesAndPermissions and editAllowedRolesAndPermissions functions in all versions up to, and including, 1.7.6. This makes it possible for unauthenticated attackers to allow lower level users to modify forms.

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 MailerLite WordPress plugin is vulnerable to an authorization bypass due to missing capability checks on two AJAX functions (toggleRolesAndPermissions and editAllowedRolesAndPermissions). These functions control which WordPress user roles can modify signup forms, but are accessible to any unauthenticated user, allowing them to elevate or modify role permissions for form editing.

MitigationUpdate the MailerLite plugin to version 1.7.7 or later, which adds the missing capability checks. Until then, consider disabling the plugin or restricting access at the server level.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify MailerLite plugin is installed
    Go to WordPress admin > Plugins and look for 'MailerLite' in the list of installed plugins. Note whether it is activated.
    Affected if Plugin is not installed or not activated means likely not affected
  2. Check installed plugin version
    In WordPress admin > Plugins > Installed Plugins, find MailerLite and read the version number displayed beneath the plugin name. Compare it to version 1.7.7.
    Affected if Version is below 1.7.7 indicates the vulnerable version is installed
  3. Confirm AJAX endpoint accessibility
    Send a GET request to /wp-admin/admin-ajax.php?action=toggleRolesAndPermissions without providing any authentication cookies or credentials. A response (rather than a 401/403 error) indicates the endpoint is exposed.
    Affected if Endpoint responds without authentication required confirms the authorization bypass is present
  4. Inspect plugin PHP for missing capability checks
    In the plugin directory (wp-content/plugins/mailerlite), locate the PHP file containing the toggleRolesAndPermissions and editAllowedRolesAndPermissions functions. Search for 'add_action' or 'add_filter' calls registering these AJAX actions and verify whether they include a capability check (such as 'current_user_can' or a permission callback) before execution.
    Affected if No capability check found before the function logic means the vulnerability is present

User is affected if the MailerLite plugin is active with a version lower than 1.7.7 and the AJAX endpoints respond without authentication.

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 MailerLite plugin to version 1.7.7 or later, which adds the missing capability checks. Until then, consider disabling the plugin or restricting access at the server level.

Recommended fix Moderate confidence

Latest stable version available in the WordPress plugin repository (after 1.7.6)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'MailerLite – Signup forms' plugin
  4. If an update is available, click 'Update Now'
  5. After updating, verify the version is newer than 1.7.6
  6. Test that the plugin functionality works correctly after the update

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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