CVE-2026-39698
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 · uneditedMissing Authorization vulnerability in PublisherDesk The Publisher Desk ads.txt the-publisher-desk-ads-txt allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects The Publisher Desk ads.txt: from n/a through <= 1.5.0.
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 · moderate confidenceMissing authorization vulnerability in The Publisher Desk ads.txt plugin allows attackers to exploit incorrectly configured access control security levels. The ads.txt file, which declares authorized ad sellers, can be accessed or modified without proper authentication/authorization checks in versions up to 1.5.0.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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.
-
Confirm PublisherDesk installationCheck your web server for PublisherDesk software by looking for its admin panel, checking installed packages, or searching for 'PublisherDesk' in application headers or source codeAffected if PublisherDesk is installed and the ads.txt feature is in use
-
Locate ads.txt fileSearch for ads.txt in the web root directory or PublisherDesk's configured content directory. Common paths include the document root or /ads/ directoryAffected if An ads.txt file exists in the application
-
Check file system permissions on ads.txtReview file system permissions (ls -la) on the ads.txt file to determine if unauthorized users can read or write to itAffected if The file has overly permissive access (world-writable or readable by unauthorized web server users)
-
Test ads.txt management interface accessAttempt to access any administrative interface for modifying ads.txt without providing credentials or with a low-privilege accountAffected if The interface allows viewing or modifying ads.txt content without proper authentication
-
Verify authorization for ads.txt operationsCheck application logs or test with different user roles to confirm whether role-based access controls are enforced on ads.txt file operationsAffected if No authorization checks are performed before allowing access to modify ads.txt content
A user is affected if PublisherDesk is installed with an accessible ads.txt file that can be read or modified without proper authentication and authorization checks.
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 dataImplement proper authorization checks for all ads.txt file access and modification operations, and ensure the plugin enforces appropriate access control policies consistent with ads.txt specifications.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39698 — 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-39698 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