dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-39292

HIGH · 7.3 CVSS v3.1 Published 2026-05-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Falco Solutions PHPPageBuilder v0.31.0 contains an unrestricted file upload vulnerability in the pagemanager/pagebuilder module that allows remote attackers to upload arbitrary files and achieve remote code execution. The vulnerability exists due to insufficient validation of uploaded file types and executable content.

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 confidence

Falco Solutions PHPPageBuilder v0.31.0 has an unrestricted file upload vulnerability in the pagemanager/pagebuilder module. The application fails to validate uploaded file types, allowing remote attackers to upload arbitrary files including executable scripts and achieve remote code execution on the server.

MitigationImplement strict whitelist-based file type validation before allowing uploads, store uploaded files outside the web root or with no-script permissions, and disable execution permissions on upload directories.

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed PHPPageBuilder version
    Locate the version file or version declaration in the PHPPageBuilder installation (commonly found in a version.php, composer.json, or configuration file in the application root). Compare the version number to v0.31.0.
    Affected if The installed version is exactly v0.31.0.
  2. Verify pagemanager/pagebuilder module presence
    Check if the pagemanager or pagebuilder module directory exists within the PHPPageBuilder installation (typically under modules/, components/, or a similar directory structure).
    Affected if The pagemanager/pagebuilder module is installed and present in the application.
  3. Confirm file upload endpoint accessibility
    Identify and access the file upload functionality within the pagemanager/pagebuilder module. Look for upload forms, API endpoints, or handling scripts (such as upload.php, save.php, or similar) in the module directory.
    Affected if The file upload functionality in the pagemanager/pagebuilder module is accessible (e.g., the route or page responds without authentication errors).
  4. Inspect file type validation logic
    Examine the upload handling code in the pagemanager/pagebuilder module for server-side file type validation. Look for checks on MIME type, file extension, or file content/magic bytes before saving uploaded files.
    Affected if The upload code lacks or has weak server-side validation (no MIME type check, no extension allowlist, no content validation).
  5. Check upload directory configuration
    Review the application configuration or upload handler to determine where uploaded files are stored and whether the upload directory is within the web root with script execution enabled.
    Affected if Uploaded files are stored in a web-accessible directory and script execution is not disabled for that directory.

A user is affected if they run PHPPageBuilder v0.31.0 with the pagemanager/pagebuilder module, the module's file upload feature is accessible, and the server-side validation is absent or insufficient.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict whitelist-based file type validation before allowing uploads, store uploaded files outside the web root or with no-script permissions, and disable execution permissions on upload directories.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-39292 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-39292 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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