CVE-2026-44958
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 · uneditedAn access control bypass allows an advertiser‑level user to activate or deactivate a banner in Revive Adserver 6.0.6 and earlier, even when such permissions were not granted. The banner-edit.php script allowed the banner status to be overwritten solely based on banner edit permissions. The status field has been removed from the hidden form fields in the banner edit screen.
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 · high confidenceRevive Adserver 6.0.6 and earlier contains an access control bypass in banner-edit.php where the banner status field could be overwritten based solely on banner edit permissions, allowing advertiser-level users to activate or deactivate banners even when they lack status-change permissions. The vulnerability stems from the status field being included in hidden form fields, enabling privilege escalation. The fix removes the status field from hidden form fields in the banner edit screen.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Revive Adserver versionLocate the version file in the Revive Adserver installation directory (typically version.txt or check the admin interface footer for the version number)Affected if The installed version is 6.0.6 or any earlier version of Revive Adserver
-
Locate banner-edit.php in the web rootNavigate to the admin directory of the Revive Adserver installation and find banner-edit.php (usually in var/www/html/revive-adserver/www/admin/banner-edit.php or similar path)Affected if The file exists in the installation
-
Inspect banner-edit.php for hidden status fieldOpen banner-edit.php in a text editor or use grep to search for the pattern 'type="hidden"' with 'name="status"' or 'name="status"' within form fieldsAffected if The file contains a hidden input field named 'status' (the vulnerable pattern that allows status modification through hidden form fields)
-
Verify user role configurationCheck the Revive Adserver user administration panel to determine if there are advertiser-level accounts that have banner edit permissions but should NOT have status-change permissionsAffected if Advertiser-level users exist with banner edit rights but without explicit status-change permissions, creating the conditions for privilege escalation
A user is affected if they are running Revive Adserver version 6.0.6 or earlier AND the banner-edit.php file contains hidden status form fields that could allow advertiser-level users to bypass permission checks for banner activation/deactivation.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade Revive Adserver to a version newer than 6.0.6, or apply the vendor patch that removes the status field from hidden form fields in banner-edit.php and implements proper permission checks for banner status changes.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44958 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-44958 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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