Volmarg Personal Management System through 2.1.0 Unrestricted File Upload RCE via /upload/send/
Affects Volmarg Personal Management System through 2.1.0 and current main, via the file-storage upload path, which has no file-type allowlist. No fixed version is listed yet.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affects all versions through v2.1.0 and current main The file-storage upload path has no file-type allowlist Depends on how the storage directory is served
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity9.6/10CVSS 8.6, total technical impact per CISA
- No patch5/5No patch listed yet
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
- Would score about 30 if CISA's SSVC rates it automatable
CVE-2026-73328 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.6 (high) and affects personal-management-system; no fixed version is listed yet.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 23/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Volmarg Personal Management System through 2.1.0 contains an unrestricted file upload vulnerability that allows authenticated users to upload PHP files via the /upload/send/ endpoint. Attackers can submit base64 fileContent with a .php fileName into the web root and request it to execute code as the web server user.
What to do
Check whether your setup matches what the bug needs.
Affects all versions through v2.1.0 and current main The file-storage upload path has no file-type allowlist Depends on how the storage directory is servedWorkaround: The facts list no workaround. The impact depends on how the storage directory is served, so preventing the web server from executing files in that directory is the factor that controls the outcome.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- volmarg personal-management-system
through 2.1.0
Evidence 7
- Report
- Repository
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-73328
Is CVE-2026-73328 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The upload path accepts files without checking their type, so an uploaded file can be a script. If the storage directory is served in a way that runs such files, this can lead to remote code execution.Source: github.com
Which versions are affected by CVE-2026-73328?
personal-management-system: through 2.1.0.Source: cve.now feed data
Am I affected, and how do I check?
The advisory says all versions through v2.1.0 and current main are affected. To check a deployment, look at the installed application version and whether it is 2.1.0 or older or a build from main, and check how the web server serves the storage directory.Source: github.com
How do I fix CVE-2026-73328?
The facts give no fixed version, so no upgrade target can be named. Check the project's repository or advisory for a release that addresses the upload path.Source: github.com
What if there's no patch?
The facts list no workaround. The impact depends on how the storage directory is served, so preventing the web server from executing files in that directory is the factor that controls the outcome.Source: github.com