CVE
Rother OSS OTOBO open redirect in ExternalURLJump action
- Exploited
- No known exploitation
- Fix
- Fixed in 10.0.13
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 10.0.13.
Summary
OTOBO 10.0.1 before 10.0.13 contains an open redirect vulnerability that allows unauthenticated attackers to redirect users by supplying arbitrary URLs to the ExternalURLJump action. Attackers can craft GET requests to /otobo/index.pl?Action=ExternalURLJump with a malicious URL parameter, which the ExternalURLJump.pm module redirects to without an allow-list check, enabling phishing attacks. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-23.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 10.0.13.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2021-48027 (Rother OSS OTOBO 10.0.1 < 10.0.13 Open Redirect via ExternalURLJump Action), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2021-48027 (entry last updated 2026-11-18):
Affected:
- Rother OSS OTOBO: from 10.0.1, fixed in 10.0.13
Fixed versions: 10.0.13.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2021-48027 is not listed as of cve.now's last read.
This KEV status is for CVE-2021-48027 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/RotherOSS/otobo/commit/de22bd995414e45f2ed60efaee4c3e62f7800dff
- https://github.com/RotherOSS/otobo/issues/1311
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/otobo-open-redirect.yaml
- https://www.vulncheck.com/advisories/rother-oss-otobo-10.0.1-before-10.0.13-open-redirect-via-externalurljump-action
- https://www.vulncheck.com/advisories/rother-oss-otobo-10.0.1-10.0.13-open-redirect-via-externalurljump-action
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2021-48027
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2021-48027"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Rother OSS OTOBO
From 10.0.1 · fixed in 10.0.13
Evidence 7
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2021-48027 |
| Record | NVD · CVE-2021-48027 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Repository | GitHub · projectdiscovery/nuclei-templates · http/vulnerabilities/other/otobo-open-redirect.yaml |
| Other links 4 | |
| Patch | GitHub · RotherOSS/otobo · Commit de22bd99 |
| Report | GitHub · RotherOSS/otobo · Issue #1311 |
| Link | vulncheck.com · advisories/rother-oss-otobo-10.0.1-before-10.0.13-open-redirect-via-externalurljump-action |
| Link | vulncheck.com · advisories/rother-oss-otobo-10.0.1-10.0.13-open-redirect-via-externalurljump-action |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2021-48027
Is CVE-2021-48027 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2021-48027?
OTOBO: from 10.0.1 before 10.0.13.Source: cve.now feed data
How do I fix CVE-2021-48027?
Upgrade to a fixed version: 10.0.13.Source: cve.now feed data