Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2024-54761: BigAnt Office Messenger 5.6.06 is vulnerable to SQL Injection via the 'dev_code' parameter.

47
This month
MEDIUM 6.3DOWNGRADE

CVE-2024-54761 is a medium-severity flaw (CVSS 6.3) affecting bigant office messenger 5. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

BigAnt Office Messenger 5.6.06 is vulnerable to SQL Injection via the 'dev_code' parameter.

Why this priority

  • Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score6.3 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionRequired
EPSS exploit chance1.8% (top 22%)
CISA exploited listNo
WeaknessCWE-89
Published2025-01-09
Last modified2026-06-17
Publisher (CNA): MITRE · Vendor: bigantsoft

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

bigantsoft bigant office messenger 5 DOWNGRADE
Affected: 5.6.0.6
Fixed in: no fixed release known
Safe to downgrade to: a release before 5.6.0.6
1. Check installed version
apt-cache policy bigant-office-messenger-5 || rpm -q bigant-office-messenger-5 || bigant-office-messenger-5 --version
2. No fixed release: DOWNGRADE to a release before 5.6.0.6 (Debian / Ubuntu)
apt-cache madison bigant-office-messenger-5 sudo apt install bigant-office-messenger-5=<VERSION_BEFORE_5.6.0.6> sudo apt-mark hold bigant-office-messenger-5
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list bigant-office-messenger-5 sudo dnf downgrade bigant-office-messenger-5-<VERSION_BEFORE_5.6.0.6> sudo dnf versionlock add bigant-office-messenger-5
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-54761?

bigant office messenger 5: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2024-54761 being exploited?

CVE-2024-54761 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-54761 affect?

CVE-2024-54761 affects bigant office messenger 5. Severity is medium (CVSS 6.3). BigAnt Office Messenger 5.6.06 is vulnerable to SQL Injection via the 'dev_code' parameter.

How urgent is CVE-2024-54761?

Priority 47/100. Public exploit reference

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.