The CVSS score on CVE-2026-18048 doesn't tell the whole story. This is a path traversal vulnerability in a WordPress photo album plugin that allows unauthenticated deletion of ZIP archives anywhere on the filesystem accessible to the web server process—including directories outside the web root like /home/user/backups/ or /var/www/backups/. The EPSS score of 0.00243 is deceptively low, but that reflects opportunistic exploitation probability, not strategic severity. The real danger is what happens when an attacker chains this with any upload or write capability: they can destroy backup archives before deploying ransomware, eliminate forensic evidence, or burn recovery paths that defenders depend on to recover from catastrophic compromises. The blast radius extends beyond the compromised site. On shared hosting infrastructure where backup directories are centralized, destroying /var/www/backups/ eliminates recovery options for every tenant on that node—not just the initially targeted site. This collapses the assumption that storage outside the web root is inherently safe. Defenders should audit their backup storage isolation, verify that the web server process lacks write permissions to backup directories, and treat any plugin with ZIP processing capabilities as a high-priority review target. The orphaned filesystem operation that makes this possible likely survived deprecation—an unmaintained code path that remained executable years after its parent function was supposedly disabled. That's the pattern: deprecation is not eradication. Prioritize plugins handling uploads or archives for removal or isolation, because the upload-to-delete-to-exploit chain is exactly how sophisticated attackers now operate.
CVE-2026-18048
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 · uneditedThe WP Photo Album Plus WordPress plugin before 9.2.07.002 does not validate a client-controlled value used to build a file path in one of its public endpoint actions, and performs no authorisation check on it, allowing unauthenticated attackers to delete arbitrary ZIP archives on the server, including ones stored outside the web root.
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 analysisA detailed technical summary for this CVE is being prepared.
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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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.
dbcve · scopedWP Photo Album Plus version 9.2.07.002 or later
- Log in to WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find WP Photo Album Plus plugin
- If update available, click 'Update Now' to update to the latest version
- Alternatively, manually update by downloading version 9.2.07.002 or later from wordpress.org/plugins/wp-photo-album-plus/ and uploading via Plugins > Add New > Upload Plugin
- Verify the installed version is 9.2.07.002 or higher after update
Generated from the published advisory — verify against the referenced sources before acting.
There is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.
Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.
We develop and verify an original fix where the vendor hasn’t, from $4,900. Deployed to your staging first — never straight to production.
Scope it with usSee what else the community needs solved on the solutions-needed board.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-18048 — 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 sourcesThe CVSS score on CVE-2026-18048 doesn't tell the whole story. This is a path traversal vulnerability in a WordPress photo album plugin that allows unauthenticated deletion of ZIP archives anywhere on the filesystem accessible to the web server process—including directories outside the web root like /home/user/backups/ or /var/www/backups/. The EPSS score of 0.00243 is deceptively low, but that reflects opportunistic exploitation probability, not strategic severity. The real danger is what happens when an attacker chains this with any upload or write capability: they can destroy backup archives before deploying ransomware, eliminate forensic evidence, or burn recovery paths that defenders depend on to recover from catastrophic compromises. The blast radius extends beyond the compromised site. On shared hosting infrastructure where backup directories are centralized, destroying /var/www/backups/ eliminates recovery options for every tenant on that node—not just the initially targeted site. This collapses the assumption that storage outside the web root is inherently safe. Defenders should audit their backup storage isolation, verify that the web server process lacks write permissions to backup directories, and treat any plugin with ZIP processing capabilities as a high-priority review target. The orphaned filesystem operation that makes this possible likely survived deprecation—an unmaintained code path that remained executable years after its parent function was supposedly disabled. That's the pattern: deprecation is not eradication. Prioritize plugins handling uploads or archives for removal or isolation, because the upload-to-delete-to-exploit chain is exactly how sophisticated attackers now operate.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-18048 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
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