CVE-2025-11581
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 · uneditedA security vulnerability has been detected in PowerJob up to 5.1.2. This vulnerability affects unknown code of the file /openApi/runJob of the component OpenAPIController. Such manipulation leads to missing authorization. The attack can be launched remotely. The exploit has been disclosed publicly and may be used.
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 confidencePowerJob versions up to 5.1.2 contain a missing authorization vulnerability in the OpenAPIController's /openApi/runJob endpoint. Remote attackers can trigger job execution without authentication or proper authorization checks, allowing unauthorized job initiation.
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<= 5.1.2CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify PowerJob installation and versionLocate the PowerJob installation directory and check the version file or JAR manifest. Common locations include /opt/powerjob, the application root, or the deployed WAR/JAR file. Look for a version file or check the jar properties.Affected if PowerJob version is 5.1.2 or lower (any version up to and including 5.1.2)
-
Verify /openApi/runJob endpoint is exposedCheck if the PowerJob web application is accessible and the OpenAPI endpoint is reachable. Attempt a GET or POST request to the /openApi/runJob path (or /openapi/runJob depending on case sensitivity). Inspect the application's exposed ports and web configuration.Affected if The /openApi/runJob endpoint is accessible from the network without being blocked by network-level restrictions
-
Test for missing authorizationSend a request to the /openApi/runJob endpoint without including any authentication tokens, headers, or session cookies. Observe whether the request is processed or rejected due to missing authorization.Affected if The endpoint accepts and processes requests without requiring authentication tokens, session cookies, or any form of authorization credentials
-
Check Spring Security or authentication configurationInspect the application's configuration files (application.yml, application.properties, or security configuration classes) for any security filters, Spring Security setup, or authentication requirements applied to the /openApi/** endpoints.Affected if No authentication or authorization rules are defined for the /openApi/runJob endpoint, or the endpoint is explicitly excluded from security filters
Your environment is affected if you are running PowerJob version 5.1.2 or lower and the /openApi/runJob endpoint is accessible without requiring authentication.
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 robust authorization checks on the /openApi/runJob endpoint to verify user permissions before allowing job execution. Consider requiring authentication tokens and validating role-based access control.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11581 — 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-2025-11581 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