dbcve.org
PowerjobApplication

CVE-2025-11580

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-10
Fix available
A fix is available. Upgrade to after 5.1.2 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 weakness has been identified in PowerJob up to 5.1.2. This affects the function list of the file /user/list. This manipulation causes missing authorization. The attack can be initiated remotely. The exploit has been made available to the public and could be used for attacks.

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

PowerJob up to version 5.1.2 contains a missing authorization vulnerability in the /user/list endpoint, allowing unauthenticated or unauthorized remote attackers to access the user list function without proper authentication checks.

MitigationUpgrade PowerJob to a version beyond 5.1.2 that includes the security patch, and review/implement proper role-based access control (RBAC) for the /user/list endpoint.

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
PowerjobApplication
Affected:<= 5.1.2

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 PowerJob installation and version
    Locate the PowerJob deployment (check application directories, Docker containers, or JAR files). Look for version information in the build artifacts, WAR/JAR file names, or check the application startup logs for the version number.
    Affected if The installed PowerJob version is 5.1.2 or lower.
  2. Confirm PowerJob web interface is accessible
    Access the PowerJob web UI (typically on port 7700 or configured port) or identify the base URL of the PowerJob server API.
    Affected if PowerJob web interface or API is reachable on the network.
  3. Test /user/list endpoint without authentication
    Send an HTTP GET request to the /user/list endpoint (e.g., curl -s http://<server>:<port>/user/list) without providing any authentication credentials (no session cookie, token, or Basic Auth).
    Affected if The endpoint returns HTTP 200 with a JSON response containing user data, indicating the user list is exposed without authorization.
  4. Verify authentication is required for other endpoints
    Compare by testing another protected endpoint like /app/list or /job/list without authentication - these should require credentials.
    Affected if Other endpoints properly require authentication while /user/list does not, confirming the authorization bypass.

You are affected if PowerJob version 5.1.2 or lower is running and the /user/list endpoint returns user data without providing any authentication credentials.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 5.1.2
Interim mitigation

Upgrade PowerJob to a version beyond 5.1.2 that includes the security patch, and review/implement proper role-based access control (RBAC) for the /user/list endpoint.

Recommended fix Moderate confidence

PowerJob 5.1.3 or later (check GitHub releases for exact version)

  1. 1. Check the official PowerJob GitHub repository (github.com/Ahoo-Wang/PowerJob) for the latest stable release
  2. 2. Look for release notes or security advisories mentioning CVE-2025-11580 or version 5.1.3+
  3. 3. Download the latest stable release (likely 5.1.3 or later) from the official releases page
  4. 4. Back up your current PowerJob configuration and database
  5. 5. Deploy the new version in a test environment first
  6. 6. Verify the /user/list endpoint now properly enforces authorization
  7. 7. After testing, deploy the updated version to production
Caveat Review release notes for potential breaking changes between 5.1.2 and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Powerjob Scoped from the published advisory
  • Consultation3.0 h
  • Implementation5.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,310
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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