dbcve.org
ParagraphsDrupal extension · Md Systems

CVE-2026-13240

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-10
Fix available
A fix is available. Upgrade to 1.21 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 6 weeks old

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 Drupal Paragraphs allows Forceful Browsing. This issue affects Paragraphs versions: from 0.0.0 to 1.21.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

Missing Authorization vulnerability in Drupal Paragraphs module allows Forceful Browsing, enabling authenticated users to access content or functionality they are not authorized to view by directly navigating to protected resources. This is a CWE-862 (Missing Authorization) issue affecting Paragraphs versions 0.0.0 through 1.21.0.

MitigationUpgrade Paragraphs module to version 1.21.1 or later which contains the authorization fix. If immediate upgrade is not possible, review and enforce role-based access controls on Paragraphs-related routes and implement proper permission checks in custom code.

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
ParagraphsDrupal extension
Affected:< 1.21

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Paragraphs module is installed
    List installed Drupal modules by examining the modules/contrib/paragraphs directory or running 'drush pm-list' to identify if the Paragraphs module is present in the codebase
    Affected if The Paragraphs module is found in the Drupal installation
  2. Identify installed Paragraphs version
    Locate the version number in the Paragraphs module's .info.yml file (typically at modules/contrib/paragraphs/paragraphs.info.yml) or composer.json file under the 'version' or 'paragraphs' package declaration
    Affected if The version is 1.21.0 or earlier (any version from 0.0.0 through 1.21.0)
  3. Confirm authenticated user access exists
    Check if the Drupal site has any user roles with authenticated access, typically by examining the users table or reviewing role configurations in the admin interface
    Affected if The site has at least one authenticated user account or role configured

A site is affected if it has the Paragraphs module installed with version 1.21.0 or earlier and allows any authenticated user access to potentially traverse protected Paragraphs-related routes.

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 1.21 or later
Fixed in 1.21
Interim mitigation

Upgrade Paragraphs module to version 1.21.1 or later which contains the authorization fix. If immediate upgrade is not possible, review and enforce role-based access controls on Paragraphs-related routes and implement proper permission checks in custom code.

Recommended fix Moderate confidence

Paragraphs 1.21 or higher

  1. 1. Back up your Drupal database and codebase before making any changes.
  2. 2. Update the Paragraphs module to version 1.21 or higher using your preferred method (e.g., Composer: `composer require drupal/paragraphs:^1.21` or through the Drupal admin interface).
  3. 3. Clear the Drupal cache after updating (e.g., `drush cr` or via the admin interface at /admin/config/development/performance).
  4. 4. Verify the update was successful by checking the Paragraphs version at /admin/modules or via `drush pm:list | grep paragraphs`.
  5. 5. Test the paragraphs functionality on your site to ensure the update did not break existing content workflows.
Caveat Review custom code that interacts with Paragraphs API, as minor version updates may include API changes; test thoroughly in a non-production environment first

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

Fix this in Paragraphs Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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