CVE-2025-46099: In Pluck CMS 4.7.20-dev, an authenticated attacker can upload or create a crafted PHP file under the albums...
In Pluck CMS 4.7.20-dev, an authenticated attacker can upload or create a crafted PHP file under the albums module directory and access it via the module routing logic in albums.site.php, resulting in arbitrary command execution through a GET parameter.
Security readout for executives and security teams
Plain-English summary
CVE-2025-46099 affects Pluck CMS 4.7.20-dev. An authenticated user can place a crafted PHP file in the albums module path and reach it through module routing, leading to arbitrary command execution. The bundle does not identify a vendor fix, supported affected versions, or active exploitation.
Executive priority
Treat as high priority for any exposed Pluck CMS 4.7.20-dev deployment, especially where multiple users can upload content. Prioritize inventory and containment first because the supplied sources do not name an official patch.
Technical view
The issue is CWE-434, unrestricted upload of a dangerous file type. The CVSS 3.1 score is 7.1 with network access, low complexity, low privileges, no user interaction, high confidentiality impact, and low integrity impact. Affected product metadata is incomplete in the supplied CVE record.
Likely exposure
Exposure appears limited to Pluck CMS 4.7.20-dev systems where authenticated users can upload or create files through the albums module. Because affected product fields are listed as n/a, teams should verify actual installed Pluck CMS versions and module usage.
Exploitation context
The source bundle supports authenticated remote exploitation potential, but not unauthenticated exploitation. KEV is false, and no cited source in the bundle confirms active exploitation in the wild. Public details describe the vulnerable routing and file handling at a high level.
Researcher notes
The CVE record gives limited affected-product metadata and one GitHub reference. Analysis should stay bounded to Pluck CMS 4.7.20-dev until vendor or project advisories clarify broader version impact, patches, or configuration-dependent exposure.
Mitigation direction
Check Pluck CMS vendor or project guidance for a fixed release or official workaround.
Restrict accounts allowed to upload or manage album module content.
Disable the albums module if it is not business-critical.
Block PHP execution from upload and module content directories where feasible.
Review web server logs for suspicious album module file access.
Validation and detection
Inventory internet-facing and internal Pluck CMS deployments.
Confirm whether any deployment runs 4.7.20-dev.
Check whether the albums module is enabled and writable by authenticated users.
Review file storage paths for unexpected PHP files under album module locations.
Confirm web server policy prevents script execution from content upload paths.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-434 · source CWE mapping
Unrestricted Upload of File with Dangerous Type
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.