Skip to content
Noroxi
NVD / CVE Program· CNA drupal

CVE-2025-31673: Drupal core - Moderately critical - Access bypass - SA-CORE-2025-002

Noroxi assessment

Priority: Monitor (action score 18/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.31% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: Drupal Drupal core 10.3.13, 10.4.3, 11.0.12.

Low priority for now. Upgrade to Drupal Drupal core 10.3.13, 10.4.3, 11.0.12 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Incorrect Authorization vulnerability in Drupal Drupal core allows Forceful Browsing.This issue affects Drupal core: from 8.0.0 before 10.3.13, from 10.4.0 before 10.4.3, from 11.0.0 before 11.0.12, from 11.1.0 before 11.1.3.

MediumCVSS 4.6 · v3.1—No exploit Fix available
Published
Mar 31, 2025
Updated
Jun 17, 2026
EPSS
0.3% · 24th percentile

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
18 / 40 · 4.6 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-31673

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for drupal records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
drupaldrupal

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • drupal drupal8.0.0 and later · before 10.3.13
  • drupal drupal10.4.0 and later · before 10.4.3
  • drupal drupal11.0.0 and later · before 11.0.12
  • drupal drupal11.1.0 and later · before 11.1.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (drupal). Independent of NVD's CPE analysis and usually ahead of it.

  • Drupal Drupal core

    • 8.0.0 and later · before 10.3.13affected · semver
    • 10.4.0 and later · before 10.4.3affected · semver
    • 11.0.0 and later · before 11.0.12affected · semver
    • 11.1.0 and later · before 11.1.3affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Packagistdrupal/corefrom 10.4.0 · before 10.4.310.4.3
Packagistdrupal/corefrom 11.0.0 · before 11.0.1211.0.12
Packagistdrupal/corefrom 11.1.0 · before 11.1.311.1.3
Packagistdrupal/corefrom 8.0.0 · before 10.3.1310.3.13

Same product

drupal: all records

Other highest-scoring records for the same primary product.

  • CVE-2018-7602Drupal core - Highly critical - Remote Code Execution - SA-CORE-2018-004KEV
    99Now
  • CVE-2018-7600Drupal before 7.58, 8.x before 8.3.9, 8.4.x before 8.4.6, and 8.5.x before 8.5.1 allows remote attackers to execute arbitrary code because…KEV
    99Now
  • CVE-2026-9082Drupal core - Highly critical - SQL injection - SA-CORE-2026-004KEV
    96Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-55637Dec 9, 2024 · Drupal core - Moderately critical - Gadget chain - SA-CORE-2024-007
    39Monitor
  • ← EarlierCVE-2024-55638Dec 9, 2024 · Drupal core - Moderately critical - Gadget chain - SA-CORE-2024-008
    39Monitor
  • Later →CVE-2025-31674Mar 31, 2025 · Drupal core - Moderately critical - Gadget Chain - SA-CORE-2025-003
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Drupal Drupal core10.3.13Vendor (CNA)
Drupal Drupal core10.4.3Vendor (CNA)
Drupal Drupal core11.0.12Vendor (CNA)
Drupal Drupal core11.1.3Vendor (CNA)
Packagist:drupal/core10.3.13Package registry (OSV)
Packagist:drupal/core10.4.3Package registry (OSV)
Packagist:drupal/core11.0.12Package registry (OSV)
Packagist:drupal/core11.1.3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
Low
Availability impact
None

Weakness class (CWE)

CWE-863 · Incorrect Authorization

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records