CVE-2023-31585
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 · uneditedGrocery-CMS-PHP-Restful-API v1.3 is vulnerable to File Upload via /admin/add-category.php.
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 confidenceGrocery-CMS-PHP-Restful-API v1.3 contains an unrestricted file upload vulnerability in the /admin/add-category.php endpoint. An unauthenticated or authenticated attacker can upload malicious PHP files (such as web shells) to the server, potentially achieving remote code execution.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 Grocery-CMS-PHP-Restful-API is installedLocate the application by searching for characteristic files such as index.php, config.php, or any PHP files containing 'Grocery' or 'CMS' in the web root directory. Check the file structure for /admin/ directory presence.Affected if The application is present on the server.
-
Identify the installed versionExamine version.php, README.md, composer.json, or any version indicator file in the application root. Run: grep -r 'version' or cat version.php 2>/dev/null to extract the version number.Affected if The version is 1.3 or falls within the v1.x range.
-
Verify the vulnerable endpoint existsCheck for the existence of /admin/add-category.php file in the web application directory. Run: find . -name 'add-category.php' -path '*/admin/*'Affected if The file /admin/add-category.php exists in the application.
-
Check if upload functionality is enabledInspect the add-category.php file for upload handling code. Look for $_FILES usage and move_uploaded_file() function calls. Verify the upload form exists in the PHP file.Affected if The endpoint contains file upload handling code and accepts file uploads.
-
Inspect upload file type validationReview the add-category.php source code for file type validation logic. Search for mime type checks, extension checks, or allowlist/blocklist implementations.Affected if There is no or weak file type validation (no strict allowlist for non-PHP files).
You are affected if Grocery-CMS-PHP-Restful-API v1.3 is installed with the /admin/add-category.php endpoint present and the file upload feature accepts files without strict validation.
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 strict allowlist-based file type validation, rename uploaded files to non-executable names, store uploads outside the web root, disable script execution in upload directories via web server configuration, and enforce authentication/authorization on the affected endpoint.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-31585 — 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-2023-31585 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