dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-3043

MEDIUM · 5.3 CVSS v3.1 Published 2025-04-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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, which was classified as critical, has been found in GuoMinJim PersonManage 1.0. This issue affects the function preHandle of the file /login/. The manipulation of the argument Request leads to path traversal. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available.

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 · moderate confidence

Path traversal vulnerability in the preHandle function of the /login/ endpoint in GuoMinJim PersonManage 1.0 allows remote attackers to manipulate the Request argument to access unauthorized files outside the web root directory via path traversal sequences (e.g., ../../).

MitigationImplement strict input validation and sanitization on the Request parameter to reject path traversal sequences; additionally, enforce proper file access controls and restrict file operations to allowed directories.

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
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. Confirm GuoMinJim PersonManage is installed
    Locate the application installation directory and identify if this specific product is deployed. Check for characteristic files such as login-related components, configuration files, or the application WAR/JAR file.
    Affected if The system has GuoMinJim PersonManage deployed and running as a web application.
  2. Verify the installed version is 1.0
    Check the application's version information through the deployment descriptor, manifest file, or application metadata. Compare against the affected version range.
    Affected if The installed version is GuoMinJim PersonManage 1.0.
  3. Confirm the /login/ endpoint is accessible
    Send an HTTP request to the /login/ endpoint of the deployed application and verify it responds. This endpoint exists in the application's routing structure.
    Affected if The /login/ endpoint is reachable and responds to HTTP requests.
  4. Test for path traversal on Request parameter
    Send a crafted request to /login/ with a Request parameter containing path traversal sequences such as ../../ to access files outside the web root. Observe if the application returns file contents or behaves differently than expected.
    Affected if The application returns file contents or allows access to files outside the designated web root directory when path traversal sequences are supplied in the Request parameter.
  5. Inspect application file access controls
    Review the application's configuration and runtime environment to determine if file operations are restricted to allowed directories or if arbitrary file access is possible.
    Affected if The application permits unrestricted file access through path traversal without proper validation or directory containment.

If GuoMinJim PersonManage version 1.0 is running with the /login/ endpoint accessible and the Request parameter accepts path traversal sequences to read files outside the web root, the environment is affected by CVE-2025-3043.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and sanitization on the Request parameter to reject path traversal sequences; additionally, enforce proper file access controls and restrict file operations to allowed directories.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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