CVE-2026-122300VulnerabilityPublished 11 Nov 2026

Apache Roller · Missing Authorization Vulnerability

Source GCVE Database

Compare

Authoritative record:CVE-2026-122300· High

Not known to be exploited · fixed in 6.1.7 : patch Apache Roller soon.

Data as of 11 Nov 2026, 16:52 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Patch: Available – fixed in 6.1.7

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-7jhv-jpvr-w92r

What to do

Affected software

Product	Affected	Fixed in
Apache Software FoundationApache Roller	Affected >=4.0 <=6.1.6	Fixed in–
Mavenorg.apache.roller/roller`pkg:maven/org.apache.roller/roller`Other threats	Affected >=4.0 <=6.1.6	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade Apache Roller to version 6.1.7 or later, where this authorization vulnerability has been fixed. No other mitigation steps are indicated.

Description

Apache Roller versions 4.0 through 6.1.6 contain a missing authorization vulnerability that allows weblog members with the Limited role to remove or modify entries they should only be able to read, including entries published by other members. This occurs because the entry editor verifies the member's weblog role but does not check if that role permits modification of the specific entry. Users are advised to upgrade to version 6.1.7 or later to address this issue.

Impact

An attacker with a Limited role can improperly modify or delete weblog entries they should only have read access to, potentially leading to unauthorized content changes and integrity violations within the weblog system.

Summary

The vulnerability in Apache Roller 4.0 through 6.1.6 is due to missing authorization checks in the entry editor component. Specifically, a weblog member assigned the Limited role can remove or change entries that they are only supposed to read, including entries created by other members. The flaw arises because the system checks the user's weblog role but fails to verify whether that role authorizes modifications on the targeted entry. This can lead to unauthorized content modification within weblogs.

CWE-862Missing Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #4OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Nov 2026, 16:52 UTC

WeaknessesCWE-862

Technical details

References

Community reviews

Related threats