dbcve.org
Edgewall TracWordPress extension · Jenkins

CVE-2023-46659

MEDIUM · 5.4 CVSS v3.1 Published 2023-10-25
Fix available
A fix is available. Upgrade to after 1.13 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Jenkins Edgewall Trac Plugin 1.13 and earlier does not escape the Trac website URL on the build page, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission.

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 Jenkins Edgewall Trac Plugin versions 1.13 and earlier fail to properly escape the Trac website URL when rendering it on the build page, creating a stored cross-site scripting (XSS) vulnerability. Attackers with Item/Configure permission can inject malicious JavaScript into the Trac URL field which executes when other users view the affected build page.

MitigationUpdate the Jenkins Edgewall Trac Plugin to version 1.14 or later, which contains the fix for proper URL escaping. If immediate patching is not possible, restrict Item/Configure permission to trusted users only.

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
Edgewall TracWordPress extension
Affected:<= 1.13

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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. Verify if Jenkins Edgewall Trac Plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Edgewall Trac' or 'Trac Plugin'. Alternatively, check the JENKINS_HOME/plugins directory for the trac-plugin folder.
    Affected if The plugin is present in the installed plugins list or filesystem
  2. Determine the installed version of the Edgewall Trac Plugin
    In Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab, find the Edgewall Trac Plugin, and note the version column. If not visible, check the plugin's manifest file (JENKINS_HOME/plugins/trac-plugin/META-INF/MANIFEST.MF) for the Plugin-Version attribute.
    Affected if The version is 1.13 or earlier
  3. Check if the plugin is configured on any jobs
    Navigate to various Jenkins jobs, click Configure, and look for a 'Trac' or 'Edgewall Trac' section. Check if a Trac website URL field is populated. Alternatively, search Jenkins configuration XML files (jobs/*/config.xml) for '<trac>' or ' trac ' configuration elements.
    Affected if The Trac URL field contains any value (even a seemingly benign one) in job configurations
  4. Identify users with Item/Configure permission
    Go to Manage Jenkins > Manage Users, then review Matrix Authorization Strategy or Project-based Authorization in Manage Jenkins > Configure Global Security. List all users or groups granted the 'Item/Configure' permission.
    Affected if Any user or group with Item/Configure permission is untrusted or if the authorization strategy allows unauthenticated or anonymous users this permission

If the Edgewall Trac Plugin versions 1.13 or earlier is installed AND configured with a Trac URL on any job AND untrusted users have Item/Configure permission, the environment is vulnerable to this XSS flaw.

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 1.13
Interim mitigation

Update the Jenkins Edgewall Trac Plugin to version 1.14 or later, which contains the fix for proper URL escaping. If immediate patching is not possible, restrict Item/Configure permission to trusted users only.

Recommended fix Moderate confidence

Jenkins Edgewall Trac Plugin version 1.14 or later

  1. Navigate to Manage Jenkins > Manage Plugins
  2. Locate the Edgewall Trac Plugin in the Installed tab
  3. Check for available updates and upgrade to the latest version
  4. Alternatively, go to the Jenkins plugin repository and download/install version 1.14 or later
  5. After upgrade, verify the plugin functions correctly with your Trac integration

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

Fix this in Edgewall Trac Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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