dbcve.org
Gemscms BackendApplication · Aptsys

CVE-2025-52023

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-23
Fix available
A fix is available. Upgrade to after 2025-05-28 or later.
See remediation →
62/100
Remediation priority · Elevated
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
A vulnerability in the PHP backend of gemscms.aptsys.com.sg thru 2025-05-28 allows unauthenticated remote attackers to trigger detailed error messages that disclose internal file paths, code snippets, and stack traces. This occurs when specially crafted HTTP GET/POST requests are sent to public API endpoints, exposing potentially sensitive information useful for further exploitation. This issue is classified under CWE-209: Information Exposure Through an Error Message.

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

This is an information disclosure vulnerability where the PHP backend exposes detailed error messages containing internal file paths, code snippets, and stack traces when malformed HTTP GET/POST requests are sent to public API endpoints. Attackers can use this information to understand the application's internal structure and identify additional vulnerabilities for exploitation.

MitigationImplement custom error handlers that display generic user-friendly messages to clients while logging detailed error information server-side for debugging. Ensure all API endpoints properly catch exceptions and return sanitized responses.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Gemscms BackendApplication
Affected:<= 2025-05-28

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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 Gemscms version
    Locate the version file or admin panel in the Aptsys Gemscms installation and record the version number or build date.
    Affected if The version or build date is 2025-05-28 or earlier.
  2. Locate API endpoint URLs
    Review the application documentation or enumerate the codebase for publicly accessible API endpoint paths (typically under /api/ or similar routes).
    Affected if Public API endpoints exist and are reachable over HTTP.
  3. Send malformed GET request to API
    Send a malformed HTTP GET request to a discovered API endpoint (e.g., missing required parameters, invalid syntax) and capture the HTTP response.
    Affected if The response contains full file paths, PHP code snippets, or detailed stack traces.
  4. Send malformed POST request to API
    Send a malformed HTTP POST request with invalid or tampered parameters to an API endpoint and capture the response.
    Affected if The response reveals internal paths, source code excerpts, or exception stack traces.
  5. Check PHP error display configuration
    Inspect the PHP configuration file (php.ini) or check the runtime configuration for display_errors and html_errors settings.
    Affected if display_errors is set to On or html_errors is enabled on a production system.

A system is affected if it runs Aptsys Gemscms Backend version dated 2025-05-28 or earlier and its API endpoints return detailed error information including file paths, code snippets, or stack traces in response to malformed requests.

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
Upgrade available Upgrade to a release after 2025-05-28
Interim mitigation

Implement custom error handlers that display generic user-friendly messages to clients while logging detailed error information server-side for debugging. Ensure all API endpoints properly catch exceptions and return sanitized responses.

Fix this in Gemscms Backend Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-52023 — 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-2025-52023 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