CVE-2026-49227Public exploitNetwork attack vector

Cross-author comment access via missing ownership check

Published Aug 18, 2026 · Updated Aug 18, 2026

Authorization bypass in Vvveb before 1.0.8.4 allows remote authenticated users to read or modify other Authors' comments via comment_id. The backend comment controllers and SQLite queries in admin/controller/content/comment.php, admin/controller/content/comments.php, and admin/sql/sqlite/comment.sql accept a caller-controlled comment_id and perform get, update, and delete operations without verifying that comment.post_id belongs to a post whose admin_id matches the current logged-in Author. Author-level access is sufficient to read pending comment text and commenter email addresses, change moderation status, edit comment content, or delete comments tied to another Author's posts.

CVSS severity7.6
High
EPSS probability0.30%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Authorization bypass in Vvveb before 1.0.8.4 allows remote authenticated users to read or modify other Authors' comments via comment_id. The backend comment controllers and SQLite queries in admin/controller/content/comment.php, admin/controller/content/comments.php, and admin/sql/sqlite/comment.sql accept a caller-controlled comment_id and perform get, update, and delete operations without verifying that comment.post_id belongs to a post whose admin_id matches the current logged-in Author. Author-level access is sufficient to read pending comment text and commenter email addresses, change moderation status, edit comment content, or delete comments tied to another Author's posts.

The record

CVE
CVE-2026-49227
Published
Aug 18, 2026
Updated
Aug 18, 2026
Vendor
givanz
Product
Vvveb
Classifications
CWE-639
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 18, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 18, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 1.0.8.4

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

givanz · Vvvebversion=< 1.0.8.4

Published CVSS scores

7.6GitHub, Inc.CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-639Authorization Bypass Through User-Controlled Key

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo