dbcve.org
Advanced Pwa Inc Push NotificationsDrupal extension · Advanced Pwa Inc Push Notifications Project

CVE-2024-13253

CRITICAL · 9.1 CVSS v3.1 Published 2025-01-09
Fix available
A fix is available. Upgrade to 8.x-1.5 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Incorrect Authorization vulnerability in Drupal Advanced PWA inc Push Notifications allows Forceful Browsing.This issue affects Advanced PWA inc Push Notifications: from 0.0.0 before 1.5.0.

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

Incorrect Authorization vulnerability in the Drupal Advanced PWA Push Notifications module allows Forceful Browsing, enabling unauthenticated or unauthorized users to directly access push notification endpoints that should require proper authentication and authorization checks.

MitigationUpdate Advanced PWA module to version 1.5.0 or later to obtain the vendor patch, and conduct a security review of all push notification endpoints to verify proper authorization controls are enforced.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Advanced Pwa Inc Push NotificationsDrupal extension
Affected:< 8.x-1.5

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
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

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. Identify if Advanced PWA module is installed
    Check your Drupal modules directory (modules/contrib/advanced_pwa or modules/custom/advanced_pwa) for the presence of the Advanced PWA module. You can also check via Drush: drush pm-list --type=module --status=enabled | grep -i advanced_pwa
    Affected if The module is not found in the Drupal installation
  2. Determine installed version of Advanced PWA module
    Check the module's composer.json file in the advanced_pwa directory for the version field, or inspect the *.info.yml file. Alternatively, in Drupal admin go to Extend and locate Advanced PWA in the module list to view the version.
    Affected if The installed version is below 8.x-1.5 (any version prior to 1.5.0)
  3. Verify if Push Notifications feature is enabled
    In Drupal admin, navigate to Configuration > Advanced PWA settings (or run: drush cget advanced_pwa.settings) and check if push_notification feature settings are present and enabled. Look for push_notification related configuration keys.
    Affected if Push Notifications feature is enabled and the module version is below 1.5.0
  4. Review access controls on push notification endpoints
    Inspect Drupal routing for push notification paths (look in advanced_pwa.routing.yml or check admin/config/system/advanced_pwa for push-related menu items). Verify that access checks are properly defined for push notification submission and management endpoints.
    Affected if Push notification endpoints are accessible without proper authorization checks or are exposed to unauthorized user roles

You are affected if the Drupal Advanced PWA module version is below 1.5.0 and the Push Notifications feature is enabled, allowing unauthorized users to access privileged push notification 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.

dbcve · scoped
Upgrade available Upgrade to 8.x-1.5 or later
Fixed in 8.x-1.5
Interim mitigation

Update Advanced PWA module to version 1.5.0 or later to obtain the vendor patch, and conduct a security review of all push notification endpoints to verify proper authorization controls are enforced.

Recommended fix High confidence

8.x-1.5

  1. 1. Back up your Drupal site database and files
  2. 2. Update the Advanced PWA inc Push Notifications module to version 8.x-1.5 or later via Drupal's module management interface or Drush command: drush up advanced_pwa_inc_push_notifications
  3. 3. Clear Drupal caches after the update: drush cr
  4. 4. Verify the module is running version 1.5.0 or later at admin/modules
  5. 5. Test that the authorization controls are properly enforced for push notification endpoints

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

Fix this in Advanced Pwa Inc Push Notifications Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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