Skip to content
Noroxi
NVD / CVE Program· CNA drupal

CVE-2017-6922: Files uploaded by anonymous users into a private file system can be accessed by other anonymous users

MediumCVSS 6.5 · v3.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 27/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: 1.9% (FIRST EPSS); higher than 80.5% of all records.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: drupal7 (Debian:7) 7.14-2+deb7u16; drupal7 (Debian:8) 7.32-1+deb8u9; drupal7 (Debian:9) 7.52-2+deb9u1.

Low priority for now. Upgrade to drupal7 (Debian:7) 7.14-2+deb7u16; drupal7 (Debian:8) 7.32-1+deb8u9; drupal7 (Debian:9) 7.52-2+deb9u1 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

In Drupal core 8.x prior to 8.3.4 and Drupal core 7.x prior to 7.56; Private files that have been uploaded by an anonymous user but not permanently attached to content on the site should only be visible to the anonymous user that uploaded them, rather than all anonymous users. Drupal core did not previously provide this protection, allowing an access bypass vulnerability to occur. This issue is mitigated by the fact that in order to be affected, the site must allow anonymous users to upload files into a private file system.

Published
Jan 22, 2019
Updated
Jun 16, 2026
EPSS
1.9% · 80th percentile

Report tools

JSON

Action score

27

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 1.9%

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-2017-6922

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 every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE 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, at most 30 a day (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
debiandebian linux

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

    • Drupal 8 and later · before 8.3.3affected
    • Drupal 7 and later · before 7.55affected
Affected versions · NVD (4)

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

  • debian debian linux8.0
  • debian debian linux9.0
  • drupal drupal7.0 and later · before 7.56
  • drupal drupal8.0.0 and later · before 8.3.4

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:7drupal7before 7.14-2+deb7u167.14-2+deb7u16
Debian:8drupal7before 7.32-1+deb8u97.32-1+deb8u9
Debian:9drupal7before 7.52-2+deb9u17.52-2+deb9u1
Packagistdrupal/corefrom 7.0 · before 7.567.56
Packagistdrupal/corefrom 8.0 · before 8.3.48.3.4
Packagistdrupal/drupalfrom 7.0 · before 7.567.56
Packagistdrupal/drupalfrom 8.0 · before 8.3.48.3.4

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-2017-6921Jan 15, 2019 · File REST resource does not properly validate
    24Monitor
  • ← EarlierCVE-2019-6338Jan 22, 2019 · third-party PEAR Archive_Tar library updates
    33Monitor
  • Later →CVE-2017-6923Jan 22, 2019 · Access bypass in Drupal 8 views
    27Monitor

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
debian:drupal77.14-2+deb7u16 · Debian:7Package registry (OSV)
Packagist:drupal/core7.56Package registry (OSV)
Packagist:drupal/core8.3.4Package registry (OSV)
Packagist:drupal/drupal7.56Package registry (OSV)
Packagist:drupal/drupal8.3.4Package 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.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-552 · Files or Directories Accessible to External Parties

CVSS vector

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

nvd-primary

Attack context

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

References

Show all references (3 more)

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

All records