dbcve.org
Gemscms BackendApplication · Aptsys

CVE-2025-52022

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 gemsloyalty.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

The PHP backend of gemsloyalty.aptsys.com.sg exposes detailed error messages including internal file paths, code snippets, and stack traces to unauthenticated users when specially crafted HTTP GET/POST requests are sent to public API endpoints. This occurs because detailed PHP error reporting is enabled in a production environment, allowing attackers to gather sensitive information about the application's internal structure.

MitigationDisable display_errors and set error_reporting to E_ALL or lower in production PHP configuration, and implement a custom error handler that logs errors server-side while returning generic error messages to users.

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 the installed version of Aptsys Gemscms Backend
    Locate the backend application files and check version metadata files, typically found in configuration files, composer.json, or a version/info file within the gemsloyalty.aptsys.com.sg application directory.
    Affected if The installed version is 2025-05-28 or earlier.
  2. Verify PHP display_errors setting
    Check the PHP configuration file (php.ini) or run phpinfo() on the server to inspect the display_errors directive.
    Affected if display_errors is set to On or On value, which allows errors to be output to the browser.
  3. Verify PHP error_reporting level
    Check php.ini or run phpinfo() to examine the error_reporting parameter.
    Affected if error_reporting is set to E_ALL or includes detailed error levels that expose stack traces and internal paths.
  4. Test API endpoints for error disclosure
    Send specially crafted HTTP GET or POST requests with invalid parameters to public API endpoints on gemsloyalty.aptsys.com.sg and observe the response.
    Affected if The response contains full file paths, code snippets, stack traces, or detailed internal error messages.
  5. Inspect web server configuration for PHP error handling
    Review the web server configuration (Apache/Nginx vhost) and any .htaccess or PHP configuration files for php_flag display_errors settings.
    Affected if display_errors is explicitly enabled in the web server configuration.

A user is affected if they are running Aptsys Gemscms Backend version 2025-05-28 or earlier AND PHP display_errors is enabled, allowing detailed error messages to be returned from API endpoints.

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

Disable display_errors and set error_reporting to E_ALL or lower in production PHP configuration, and implement a custom error handler that logs errors server-side while returning generic error messages to users.

Fix this in Gemscms Backend Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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