dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-9376

MEDIUM · 6.3 CVSS v3.1 Published 2026-05-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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 was determined in JPress up to 1.0.3. The affected element is an unknown function of the file /ucenter/article/doWriteSave of the component UCenter Article Submission Endpoint. Executing a manipulation of the argument id/userId can lead to improper authorization. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized. The project was informed of the problem early through an issue report but has not responded yet.

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

JPress up to 1.0.3 contains an improper authorization vulnerability in the UCenter article submission endpoint (/ucenter/article/doWriteSave). By manipulating the id/userId parameters, an attacker can bypass authorization checks and potentially modify or submit articles belonging to other users.

MitigationImplement proper authorization validation ensuring users can only access and modify their own articles. All article operations should verify the authenticated user matches the resource owner before allowing any write operations.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 JPress installation
    Locate JPress by searching for characteristic files such as pom.xml, build.gradle, or the presence of the 'io.jpress' package structure in the application directory. Check the web root for JPress-specific artifacts like 'jpress' folders or WAR files.
    Affected if JPress is present and the version is 1.0.3 or earlier.
  2. Determine installed JPress version
    Inspect the pom.xml file in the JPress installation directory for the <version> element, or check the build.gradle file if Gradle-based. Alternatively, look for a version manifest or check the about page in the admin panel if accessible.
    Affected if The version listed is 1.0.3 or any earlier version.
  3. Verify /ucenter/article/doWriteSave endpoint exists
    Review the application source code or decompiled classes to confirm the presence of the ArticleController or equivalent class handling the '/ucenter/article/doWriteSave' route. Check the web.xml or routing configuration for this endpoint mapping.
    Affected if The endpoint is present in the deployed application.
  4. Check if ucenter module is enabled
    Inspect the JPress configuration files (such as application.properties or config.yaml) for module settings. Verify that the 'ucenter' user center module is not disabled. Check database tables related to module configuration if applicable.
    Affected if The ucenter module is enabled and accessible to users.
  5. Confirm authorization logic on the endpoint
    Examine the source code of the doWriteSave handler in the ArticleController. Look for code that retrieves the 'id' or 'userId' parameters from the request and verify whether proper ownership validation occurs before allowing article creation or modification. Search for getCurrentUser or similar authorization checks.
    Affected if The endpoint allows manipulation of id or userId parameters without verifying that the authenticated user owns the article or has permission to act on behalf of the specified user.

You are affected if JPress version 1.0.3 or earlier is installed, the /ucenter/article/doWriteSave endpoint exists, and the ucenter module is enabled without proper authorization validation on the id/userId parameters.

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 proper authorization validation ensuring users can only access and modify their own articles. All article operations should verify the authenticated user matches the resource owner before allowing any write operations.

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-2026-9376 — 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-2026-9376 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