CVE-2023-41260
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 · uneditedBest Practical Request Tracker (RT) before 4.4.7 and 5.x before 5.0.5 allows Information Exposure in responses to mail-gateway REST API calls.
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 confidenceInformation exposure vulnerability in Best Practical Request Tracker's mail-gateway REST API allows sensitive data to be disclosed in API responses. Affected versions are RT 4.x before 4.4.7 and 5.x before 5.0.5.
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< 4.4.7>= 5.0.0, < 5.0.5CVSS 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.
-
Determine installed RT versionRun 'rt-version' from the RT bin directory, or check the VERSION file in the RT installation root, or log into the RT web interface and navigate to Tools > AboutAffected if Version is 4.x before 4.4.7 OR version is 5.x before 5.0.5
-
Confirm mail-gateway REST API is in useCheck RT_SiteConfig.pm for RT::MailGateway enablement or examine your RT mail gateway logs for REST API activity; also verify if /REST/1.0/NoAuth/mail-gateway endpoint is accessibleAffected if Mail-gateway REST API endpoint is accessible and being used
-
Inspect API response for data exposureSend a test request to the mail-gateway REST endpoint (e.g., curl http://your-rt-server/REST/1.0/NoAuth/mail-gateway) and examine the response for sensitive data that should not be disclosedAffected if API responses contain sensitive information that should not be exposed (such as configuration details, user data, or internal system information)
You are affected if your RT version is below 4.4.7 or below 5.0.5 AND the mail-gateway REST API is enabled and returning sensitive data in responses.
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.
dbcve · scoped4.4.75.0.5
Upgrade RT to version 4.4.7 or 5.0.5 (depending on your branch) to remediate the information exposure. Test mail-gateway functionality after upgrading.
RT 4.4.7 (for 4.x branch) or RT 5.0.5 (for 5.x branch)
- 1. Back up your entire Request Tracker installation directory and database before proceeding
- 2. Determine your current RT version by checking the version file or running `perl -Ilib -MRT -e 'print RT->Version;'
- 3. If running RT 4.x, upgrade to version 4.4.7; if running RT 5.x, upgrade to version 5.0.5
- 4. Download the appropriate tarball from https://download.bestpractical.com/
- 5. Extract the new version and follow the installation instructions in README or UPGRADING files
- 6. Run the upgrade script (typically `make upgrade`) to update the database schema
- 7. Restart all RT services (web server, mail gateway, cron jobs)
- 8. Verify the version number shows the updated release and test mail-gateway REST API functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41260 — 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-2023-41260 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