dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2025-12349

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-19
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 Icegram Express - Email Subscribers, Newsletters and Marketing Automation Plugin for WordPress is vulnerable to Authorization in versions up to, and including, 5.9.10. This is due to the plugin not properly verifying that a user is authorized to perform an action in the `trigger_mailing_queue_sending` function. This makes it possible for unauthenticated attackers to force immediate email sending, bypass the schedule, increase server load, and change plugin state (e.g., last-cron-hit), enabling abuse or DoS-like effects.

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 Icegram Express WordPress plugin lacks proper authorization validation in the trigger_mailing_queue_sending function, allowing unauthenticated users to trigger email queue processing. Attackers can abuse this to force immediate email dispatch, bypass scheduled sending, manipulate plugin state (like last-cron-hit timestamps), and cause denial-of-service conditions through resource exhaustion.

MitigationUpdate to the latest patched version of Icegram Express which implements proper capability and authorization checks in the trigger_mailing_queue_sending function. Until patched, consider disabling or restricting access to the mailing queue functionality via server-level controls.

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. Confirm Icegram Express is installed
    Navigate to WordPress admin > Plugins and locate 'Icegram Express' in the list of installed plugins
    Affected if The plugin appears in the installed plugins list
  2. Identify the installed version
    Click on the plugin to view its details, or check the plugin header in /wp-content/plugins/icegram-express/icegram-express.php for the 'Version' field
    Affected if The version displayed cannot be confirmed as patched (no specific safe version was provided in the CVE data)
  3. Verify the plugin is active
    In WordPress admin > Plugins, check if Icegram Express shows as 'Active'
    Affected if The plugin status is Active
  4. Check if the mailing queue trigger is exposed
    Inspect the site for accessible endpoints that call trigger_mailing_queue_sending, such as wp-admin/admin-ajax.php?action=icegramExpress_trigger_mailing_queue or similar AJAX actions; also check for any publicly accessible cron job URLs pointing to the plugin
    Affected if The trigger function is reachable without authentication (the vulnerability condition)
  5. Review access logs for suspicious queue triggers
    Examine web server access logs (Apache/Nginx) for requests to AJAX or cron endpoints related to icegram Express that originate from unauthenticated IP addresses
    Affected if Unauthenticated requests to plugin mailing queue triggers are present in logs

If Icegram Express is installed, active, and its mailing queue trigger function is accessible without authentication, the environment is affected by this authorization bypass vulnerability.

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 Icegram Express which implements proper capability and authorization checks in the trigger_mailing_queue_sending function. Until patched, consider disabling or restricting access to the mailing queue functionality via server-level controls.

Recommended fix High confidence

Upgrade to Icegram Express version 5.9.11 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Icegram Express' (or 'Email Subscribers, Newsletters and Marketing Automation Plugin')
  4. If an update is available, click 'Update Now' to update to the latest version
  5. Alternatively, download the latest version from wordpress.org/plugins/icegram-express and upload manually via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin version is 5.9.11 or higher under Plugins > Installed Plugins

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
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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